From: | "fkater(at)googlemail(dot)com" <fkater(at)googlemail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: OIDs depending data -- how to dump/restore? |
Date: | 2010-03-14 20:09:37 |
Message-ID: | 20100314200937.GA2168@comppasch2 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver:
> > AFAIK the dump/restore does not rebuild the original OID
> > values, so all relations built accross OIDs fail.
> >
> > (1)
> > Is there a way to keep the original OID values somehow?
>
> From here:
> http://www.postgresql.org/docs/8.4/interactive/app-pgdump.html
>
> -o
> --oids
>
> Dump object identifiers (OIDs) as part of the data for every table. Use this
> option if your application references the OID columns in some way (e.g., in a
> foreign key constraint). Otherwise, this option should not be used.
Thanks, but the problem is *restoring* OIDs afterwards,
isn't it? AFAIK the OIDs being restored are not the same
values as the ones being saved, so my internal relations to
those OIDs are all mixed up after a restore.
I'd be happy if someone told me that this was wrong. :-)
Felix
From | Date | Subject | |
---|---|---|---|
Next Message | Gordon Shannon | 2010-03-14 20:11:50 | Re: unexplained autovacuum to prevent wraparound |
Previous Message | Tom Lane | 2010-03-14 19:23:36 | Re: Re: Is there any easy way to determine a default value specified for table column? |