| From: | Jim Nasby <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Florian G(dot) Pflug <fgp(at)phlo(dot)org> |
| Cc: | Nitin Verma <nitinverma(at)azulsystems(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: VACUUMing sometimes increasing database size / sometimes |
| Date: | 2006-06-15 20:24:10 |
| Message-ID: | 6B94D222-5A5F-487F-AC0B-BA1877394AFE@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chander Ganesan | 2006-06-16 03:13:23 | Omitting tablespace creation from pg_dumpall... |
| Previous Message | Jim Nasby | 2006-06-15 20:21:29 | Re: Annoying "could not find a "psql" to execute" message |