Re: Dumpall without OID

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: Girts Laudaks <laudaksg(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Dumpall without OID
Date: 2011-01-27 19:33:27
Message-ID: 4D41C887.1060806@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 01/27/2011 04:52 AM, Girts Laudaks wrote:
> Hi,
>
> What could be the possible damage if a database is migraged without the
> -o (OID) option? Integrity of data?

User OIDs are deprecated,so the main problem is whether you are
currently using them as foreign keys. If you do not specify the -o
switch and have OIDs specifically defined for a table(not the default)
then new ones will be generated when the data is restored. If your
schema/app depend on the old numbers then it would be a problem.

> What are the options to solve this problem if it is migrated this way?
> Shouldn't pg_dumpall work like an exact copy of db?
> What could have gone wrong if only these commands were used?
>
> pg_dumpall -v -U postgres | gzip > /var/lib/pgsql/dump.data.gz
> gunzip -c /var/lib/pgsql/dump.data.gz | psql -U postgres >> /tmp/import.log
>
> They were used to migrate from PG8.4 to PG9
>
> Regards,
> Girts
>

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Browne 2011-01-27 19:35:55 Re: Adding ddl audit trigger
Previous Message Alban Hertroys 2011-01-27 18:14:42 Re: Select query ignores index on large table