Will 7.3.2 Dump made up of copies using pg_dump import without any migration
to 8.0+? What I need isn't a once process and will go as a automated script,
in a way that user will not even get to know (if he isn't reading that logs)
Database version changed. Considering that even a remote problem in export
and import across versions may hit. So please let me know all the do's and
don'ts... or the pointers to those.
-----Original Message-----
From: Jim Nasby [mailto:jnasby@pervasive.com]
Sent: Friday, June 16, 2006 1:54 AM
To: Florian G.Pflug
Cc: Nitin Verma; pgsql-general@postgresql.org
Subject: Re: [GENERAL] VACUUMing sometimes increasing database size /
sometimes
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