From: Tim Gustafson <tjg@soe.ucsc.edu>
To: pgsql-admin@postgresql.org
Subject: Problems With pg_dumpall and OIDs
Date: Wed, 19 Nov 2008 14:35:54 -0800 (PST)
Message-ID: <623884546.38971227134154902.JavaMail.root@mail-01.cse.ucsc.edu> (raw)
Hello,
I currently have a old GForge installation running on Postgres 7.4.19. GForge relies on the OID columns of their application tables for different things. I'm trying to upgrade Postgres to 8.2, and in order to do so, I'm doing:
pg_dumpall --oids --clean > foo.sql
However, the "CREATE TABLE" statements in foo.sql don't have "WITH OIDS" specified, so when the tables are created in the new server, they are not getting OID columns, and then the data load portion of the SQL script appears to essentially be ignoring the OID information.
Is there an updated pg_dumpall that fixes this problem? Was this a known issue in the 7.4.19 pg_dumpall that was fixed? Any suggestions on how best to get the data out of the 7.4 server and in to the 8.2 server while maintaining all the OID information?
Thanks for all your help!
Tim Gustafson
SOE Webmaster
UC Santa Cruz
tjg@soe.ucsc.edu
831-459-5354
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tjg@soe.ucsc.edu
Subject: Re: Problems With pg_dumpall and OIDs
In-Reply-To: <623884546.38971227134154902.JavaMail.root@mail-01.cse.ucsc.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox