| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Audit of logout |
| Date: | 2014-07-02 20:52:43 |
| Message-ID: | 22984.1404334363@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> In short, maybe we ought to invent a new category PGC_SU_BACKEND (not
> wedded to this spelling), which is to PGC_BACKEND as PGC_SUSET is to
> PGC_USERSET, ie same when-it-can-be-changed behavior but only superusers
> are allowed to change it. I don't have any objection to making these two
> settings only adjustable by superusers --- I just don't want to give up
> the existing timing restrictions for them.
Another idea would be to get rid of PGC_SUSET as a separate category, and
instead have a superuser-only bit in the GUC flags, which would apply to
all categories. This would be a bit more orthogonal, though likely a
much more invasive change.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2014-07-02 21:00:45 | Re: Patch to send transaction commit/rollback stats to the stats collector unconditionally. |
| Previous Message | Alvaro Herrera | 2014-07-02 20:47:16 | Re: Audit of logout |