Re: Permanent settings

From: "Dawid Kuroczko" <qnex42(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Josh Berkus" <josh(at)agliodbs(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Dimitri Fontaine" <dfontaine(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org, "Magnus Hagander" <magnus(at)hagander(dot)net>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Csaba Nagy" <nagy(at)ecircle-ag(dot)com>, "Aidan Van Dyk" <aidan(at)highrise(dot)ca>
Subject: Re: Permanent settings
Date: 2008-02-20 21:27:26
Message-ID: 758d5e7f0802201327j16b378fat7e9c5e76f5f73a58@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 20, 2008 at 7:34 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>
> > 2) allow *commenting* of pg_settings / SET PERMANENT. Thus:
>
> > SET PERMANENT work_mem = '12mb' COMMENT '16mb too high; OOM';
>
> Ugh :-(
>
> I think that putting this into SET is a pretty bad idea in any case.
> SET is, and always has been, a session-local operation. Providing a
> secondary option that transforms it into something completely different

I think that's valid argument.

We already have ALTER USER foo SET bar = baz, so why not something like:

ALTER CLUSTER SET shared_buffers TO '2GB';

...perhaps with some other word than CLUSTER?

Regards,
Dawid

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-02-20 21:35:15 Re: Why does pg_ctl.c have its own copy of PM_VERSIONSTR?
Previous Message Andrew Dunstan 2008-02-20 21:20:22 Re: Why does pg_ctl.c have its own copy of PM_VERSIONSTR?