I do not see an option on the man page for pg_dumpall that directs it to
the data of a different version on a different filesystem. I would greatly
appreciate learning the correct syntax that will allow me to use the
pg_dumpall from 8.3.3 to extract all data from the 8.1.4 version residing in
On 18/06/2008 15:16, Rich Shepard wrote:
I do not see an option on the man page for pg_dumpall that directs it to
the data of a different version on a different filesystem. I would greatly
appreciate learning the correct syntax that will allow me to use the
pg_dumpall from 8.3.3 to extract
am Wed, dem 18.06.2008, um 7:16:11 -0700 mailte Rich Shepard folgendes:
I do not see an option on the man page for pg_dumpall that directs it to
the data of a different version on a different filesystem. I would greatly
appreciate learning the correct syntax that will allow me to use the
On Wed, Jun 18, 2008 at 07:16:11AM -0700, Rich Shepard wrote:
pg_dumpall from 8.3.3 to extract all data from the 8.1.4 version residing in
/usr4/pgsql_old/data/ and write it to a file (with the -f option) in
/usr4/postgres-backups.
Can't do it. Start the old postmaster with -D
On Wed, 18 Jun 2008, Andrew Sullivan wrote:
Can't do it. Start the old postmaster with -D /usr4/pgsql_old/data, and
then use pg_dumpall against that backend.
Andrew,
When I try, I see:
[EMAIL PROTECTED]:/var/lib/pgsql$ postgres -D /usr4/pgsql_old/data
FATAL: database files are
On Wed, 2008-06-18 at 08:55 -0700, Rich Shepard wrote:
On Wed, 18 Jun 2008, Andrew Sullivan wrote:
Can't do it. Start the old postmaster with -D /usr4/pgsql_old/data, and
then use pg_dumpall against that backend.
Andrew,
When I try, I see:
[EMAIL PROTECTED]:/var/lib/pgsql$
On Wed, 18 Jun 2008, Joshua D. Drake wrote:
This is what I suggest:
download 8.1.13:
unpack; then:
Done.
./configure --prefix=/tmp/pg813; make install
cd /tmp/pg813
bin/pg_ctl -D /usr4/pgsql_old/data start
cd /
/usr/bin/pg_dumpall -U user mydatabase.sql
Modified above a bit. I used
On Wed, 2008-06-18 at 10:23 -0700, Rich Shepard wrote:
On Wed, 18 Jun 2008, Joshua D. Drake wrote:
Then you can reinitialize a new cluster with initdb here:
/var/lib/pgsql/data (you will have to remove the old one)
As user postgres, I cleaned out /var/lib/pgsql/data/* and
On Wed, 18 Jun 2008, Joshua D. Drake wrote:
You need to remove the directory, not the files underneath then:
Ah, so.
Redid, after removing /var/lib/pgsql/data
Then restore as normal using psql -U postgres mydatabase.sql
Postgres is now running (whew!), but I'm still doing
On Wed, Jun 18, 2008 at 10:42:51AM -0700, Rich Shepard wrote:
[EMAIL PROTECTED] /usr4/postgres-backups]$ pg_restore -U postgres
pg814data.sql
pg_restore: [archiver] input file does not appear to be a valid archive
But it was created using the 8.3.3 pg_dumpall in /usr/bin/.
Did you use a
On Wed, Jun 18, 2008 at 10:42:51AM -0700, Rich Shepard wrote:
[EMAIL PROTECTED] /usr4/postgres-backups]$ pg_restore -U postgres
pg814data.sql
pg_restore: [archiver] input file does not appear to be a valid archive
But it was created using the 8.3.3 pg_dumpall in /usr/bin/.
pgdumpall
On Wed, 18 Jun 2008, Andrew Sullivan wrote:
Did you use a non-ascii dump format? Try
Andrew,
Not by design.
psql -U postgres -f pg814data.sql
Well! That stirred things up. I seem to have restored the accounting data
(and the other databases in the cluster), but cannot access
12 matches
Mail list logo
