On Wed, Jul 27, 2011 at 7:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Phil Sorber <phil(at)omniti(dot)com> writes:
>> Currently if you use 'ALTER ROLE rolename SET ROLE', pg_dumpall will
>> dump an 'ALTER ROLE' out right after the 'CREATE ROLE' statement.
> I think pg_dumpall is the very least of your problems if you do
> something like that. We probably ought to forbid it entirely.
Well, we had a long discussion of that on the thread Phil linked to,
and I don't think there was any consensus that forbidding it was the
right thing to do. Phil appears to be trying to implement the
proposal you made here:
...although I don't think that what he did quite matches what you asked for.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2011-07-28 13:46:41|
|Subject: Re: error: could not find pg_class tuple for index 2662|
|Previous:||From: Nikhil Sontakke||Date: 2011-07-28 13:43:50|
|Subject: Re: Check constraints on partition parents only?|