Tue Jun 6 08:38:01 PDT 2006
- Previous message: [Slony1-general] Large initial COPY transaction and a possible solution for the provider
- Next message: [Slony1-general] Slony-I 1.2 - Forging Towards Release
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, May 31, 2006 at 09:33:04PM +0000, Christopher Browne wrote: > Based on the discussion of the last day or so, we really need to see > about getting version 1.2 released. > > As far as I can tell, all of the issues Rod pointed out are resolved in > CVS HEAD, so that 1.2 should seriously diminish the need for > "super-skilled staff" when setting up Very Large Instances. Some issues > do not disappear; there will still be long running transactions that > cause some inconvenience, which is, to a great degree, an unavoidable > problem. But we can certainly get rid of a bunch of the "misfeature" cases. There's some ideas in http://archives.postgresql.org/pgsql-hackers/2006-02/msg01164.php that could potentially eliminate the issues associated with long-running transactions, should someone want to push for it. In a nutshell, the idea is to provide a means for a transaction to list a set of tables that it will never touch (again). Vacuum can then take that into account when figuring out what the minimum XID that has to be kept in a table is. -- 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] Large initial COPY transaction and a possible solution for the provider
- Next message: [Slony1-general] Slony-I 1.2 - Forging Towards Release
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list