Re: superuser unable to modify settings of a system table - Mailing list pgsql-bugs

From Gurjeet Singh
Subject Re: superuser unable to modify settings of a system table
Date
Msg-id AANLkTilTjK0E0w_mWlT54vAn50i_JXW1idTVc-yA8aQg@mail.gmail.com
Whole thread Raw
In response to Re: superuser unable to modify settings of a system table  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: superuser unable to modify settings of a system table
List pgsql-bugs
On Thu, Jun 3, 2010 at 1:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Gurjeet Singh <singh.gurjeet@gmail.com> writes:
> > On PG 8.4.4 I am unable to set per-table autovacuum setting for the
> > pg_listener table. Being a superuser, I'd expect Postgres to allow me to
> do
> > that.
>
> See allow_system_table_mods.  Even superusers should think twice before
> fooling with system catalogs...
>
>
:) Well, I assume a lot of thought does go into the process of altering the
system table, but when it is needed, it is really needed.

In the setup that I am handling right now, LISTEN/NOTIFY gets used a lot,
and allowing autovacuum to manage it with default settings is really counter
productive.

allow_system_table_mods needs a restart :( .Yet another parameter I wish was
changeable on the fly.

Regards,
--
gurjeet.singh
@ EnterpriseDB - The Enterprise Postgres Company
http://www.EnterpriseDB.com

singh.gurjeet@{ gmail | yahoo }.com
Twitter/Skype: singh_gurjeet

Mail sent from my BlackLaptop device

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: superuser unable to modify settings of a system table
Next
From: Hartmut Goebel
Date:
Subject: Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading