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 15:08:05 |
Message-ID: | 2585.1258124885@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:
> I think it would be over the top to suggest that pg_dump has to cope
> with modifications that can only occur through manual updates to the
> system catalogs, but it seems like anything that can be done using DDL
> statements should be handled.
Like, say, DELETE FROM pg_proc?
Basically, if you use superuser powers to fool with the definition of
any system object, it's on your own head whether the result works at all
and whether or how to preserve that change into a new version of
Postgres. I do not think it's part of pg_dump's charter to try to
handle that. In a significant fraction of cases, preserving the change
would be exactly the wrong thing, but there is no way for pg_dump to
know the difference.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2009-11-13 15:39:32 | Re: BUG #5184: default tablespace owner is not dumped |
Previous Message | Robert Haas | 2009-11-13 12:29:05 | Re: BUG #5184: default tablespace owner is not dumped |