Thread: VACUUMing sometimes increasing database size / sometimes crashing it
Were these bugs fixed by 7.3.2, if not what version should I look for? http://archives.postgresql.org/pgsql-admin/2001-06/msg00005.php http://archives.postgresql.org/pgsql-hackers/2000-04/msg00083.php It would be gr8 if can myself look into bug list next time before asking questions, any URL?
Nitin Verma wrote: > Were these bugs fixed by 7.3.2, if not what version should I look for? > > http://archives.postgresql.org/pgsql-admin/2001-06/msg00005.php > http://archives.postgresql.org/pgsql-hackers/2000-04/msg00083.php Ahm... 7.3.2 is *very* outdated. The current version of postgresql is 8.1.4. The mails you linked are from the year 2001 (!), and concern 6.5 (!!) - A lot of things have changed in postgres since then ;-) None of the problems discussed there should trouble postgres anymore, if you use a at least remotely recent version (Say, >= 8.0, or 7.4 *at* *the* *very* *least*). greetings, Florian Pflug
On Jun 15, 2006, at 1:16 PM, Florian G. Pflug wrote: > Nitin Verma wrote: >> Were these bugs fixed by 7.3.2, if not what version should I look >> for? >> http://archives.postgresql.org/pgsql-admin/2001-06/msg00005.php >> http://archives.postgresql.org/pgsql-hackers/2000-04/msg00083.php > Ahm... 7.3.2 is *very* outdated. The current version of postgresql is > 8.1.4. > > The mails you linked are from the year 2001 (!), and concern 6.5 > (!!) - A lot of things have changed in postgres since then ;-) > > None of the problems discussed there should trouble postgres > anymore, if > you use a at least remotely recent version (Say, >= 8.0, or 7.4 > *at* *the* *very* *least*). And if you are going to stick with 7.3, at least get the latest version of it. As for searching for bugs... http://archives.postgresql.org/pgsql-bugs/ -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461