| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Natalie Wenz <nataliewenz(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_dump: preserving oids in system tables? |
| Date: | 2015-05-06 20:03:36 |
| Message-ID: | CAKFQuwZcYN8LYuO2Aw9gnF=wsMJWjOP7_CGJJu=x5KdoyCbQPQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, May 6, 2015 at 11:11 AM, Natalie Wenz <nataliewenz(at)gmail(dot)com> wrote:
> Can someone confirm something for me? It seems that pg_dump with the -o
> option preserves OIDS for user objects, but does not preserve the OIDs for
> objects in system tables. Is that correct?
>
>
[...]
> The app has a table that associates a user (role) with a "department" by
> inserting a row into a table with the values 'usesysid' from pg_user and a
> department
"pg_dump" doesn't dump roles. They are global and handled via
"pg_dumpall".
http://www.postgresql.org/docs/9.4/static/app-pg-dumpall.html
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-06 20:16:04 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Previous Message | Heikki Linnakangas | 2015-05-06 19:51:43 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |