From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5184: default tablespace owner is not dumped |
Date: | 2009-11-13 06:13:32 |
Message-ID: | 25166.1258092812@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Robert Haas" <robertmhaas(at)gmail(dot)com> writes:
> The following command does not change the output of "pg_dumpall":
> alter tablespace pg_default owner to bob;
I don't think this is a bug. It's one specific aspect of a general
principle that system objects don't get dumped. If they did, using
pg_dump to upgrade across major versions would be somewhere between
impossible and your worst nightmare.
It might be nice if manual changes to system objects got dumped,
but that's really an AI-complete problem --- which properties of
the objects represent manual changes, and how can we know whether
trying to apply those changes to a new system version will work?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Siwat Siwarborvorn | 2009-11-13 08:07:32 | BUG #5185: postgres error "invalid page header in block xx of relation "pg_proc_proname_args_nsp_index" |
Previous Message | Robert Haas | 2009-11-13 05:34:20 | BUG #5184: default tablespace owner is not dumped |