Re: superuser unable to modify settings of a system table

From: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PGSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: superuser unable to modify settings of a system table
Date: 2010-06-03 17:14:06
Message-ID: AANLkTilTjK0E0w_mWlT54vAn50i_JXW1idTVc-yA8aQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Jun 3, 2010 at 1:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)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(dot)gurjeet(at){ gmail | yahoo }.com
Twitter/Skype: singh_gurjeet

Mail sent from my BlackLaptop device

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-06-03 17:21:29 Re: superuser unable to modify settings of a system table
Previous Message Tom Lane 2010-06-03 17:02:23 Re: superuser unable to modify settings of a system table