Tue Mar 7 11:18:56 PST 2006
- Previous message: [Slony1-general] What is left for 1.2???
- Next message: [Slony1-general] Exuberant Subscriber Table Locking at Subscribe Time
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Mar 07, 2006 at 03:36:57PM +0800, Christopher Kings-Lynne wrote: > > What used to happen is that the tables would gradually get locked, > > piecemeal, as Slony-I got to each one. You could run into deadlock > > problems right near the end, which is a real waste. By locking them > > up front, any failures will take place before any data is copied, so > > this minimizes time wastage. > > Which is exactly why pg_dump does the saem thing. Wait, are we talking about exclusive locks here? Or do we just aquire shared locks to prevent anyone from running DDL against the objects? -- Jim C. Nasby, Sr. Engineering Consultant jnasby at pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
- Previous message: [Slony1-general] What is left for 1.2???
- Next message: [Slony1-general] Exuberant Subscriber Table Locking at Subscribe Time
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list