On Thu, Jun 3, 2010 at 1:21 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> writes:
>> allow_system_table_mods needs a restart :( .Yet another parameter I wish was
>> changeable on the fly.
> I'm not sure there's any compelling reason why it couldn't be SUSET.
> Maybe a TODO ...
Personally, I think it would be better to put some work into making
allow_system_table_mods a little less simple-minded. Right now,
!allow_system_table_mods prohibits you from doing perfectly sensible
things (as in the OP's original example) yet still allows you to do
things that are totally nuts (like DELETE FROM pg_class, which causes
every subsequent connection attempt for that database to panic).
Perfection may be too much to ask for but I'd take "modest
The Enterprise Postgres Company
In response to
pgsql-bugs by date
|Next:||From: Bernd Helmle||Date: 2010-06-04 20:50:51|
|Subject: Re: BUG #5488: pg_dump does not quote column names ->
pg_restore may fail when upgrading|
|Previous:||From: Greg Stark||Date: 2010-06-04 20:18:24|
|Subject: Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail|