e
running 7.2.X.
Migration to version 7.2.1 A dump/restore is *not* required for those
running 7.2.
Migration to version 7.2A dump/restore using "pg_dump" is required
for those wishing to migrate data from any previous release.
Best regards,
Stephane Charette
stephanechar
ng other things) upgrade the database to 7.2.3.
Is a dump/restore required from 7.2 to 7.2.3? What if we were to go
from 7.2 to 7.2.4, or even from 7.2 to the latest, 7.3.2? How can we
tell when a dump/restore is required?
Thanks,
Stephane Charette
stephanecharette at
ut no many suggestions or
solutions.
In our case, we are using 7.2 on a linux 2.2.14 kernel. Binaries were
downloaded via RPM directly from RedHat.
My questions now would be:
1) How serious is the vacuumdb error?
2) How do we fix it?
3) Is the database hosed?
Thanks in advance,
Stephane Charette
umber is perhaps not being displayed. All of the
shell scripts in .../pgsql/bin/ contain the word "7.2" -- no mention of
minor version numbers such as "7.2.0", "7.2.1", etc.
(Next time we'll skip the binaries and download & compile
nel 2.2.14;
postmaster is running with the following command-line:
"/usr/local/pgsql/bin/postmaster -D /foo/data -S"; haven't changed any
of the default tuning values in the p*.conf files.)
Thanks in advance for any assistance you can provide,
Stephane Charette
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
o for a database integrity check?
Is there a better way to do this than a vacuum?
Stephane Charette
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
