Re: [HACKERS] Userset logging

Lists: pgsql-hackerspgsql-patches
From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Userset logging
Date: 2008-07-07 15:13:13
Message-ID: 1215443593.4051.601.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers pgsql-patches

I notice log_temp_files is a PGC_USERSET parameter, which is out of step
with our current thinking on who is allowed to initiate logging.

Is there a rationale for this? Or should we set this to PGC_SUSET like
all the other logging functions?

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support


From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: List pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Userset logging
Date: 2008-07-08 07:36:21
Message-ID: 1215502581.4051.674.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers pgsql-patches


On Mon, 2008-07-07 at 16:13 +0100, Simon Riggs wrote:
> I notice log_temp_files is a PGC_USERSET parameter, which is out of step
> with our current thinking on who is allowed to initiate logging.
>
> Is there a rationale for this? Or should we set this to PGC_SUSET like
> all the other logging functions?

Patch enclosed.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

Attachment Content-Type Size
log_temp_files_suset.v1.patch text/x-patch 924 bytes

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: List pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Userset logging
Date: 2008-08-22 18:47:14
Message-ID: 200808221847.m7MIlEQ05484@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers pgsql-patches

Simon Riggs wrote:
>
> On Mon, 2008-07-07 at 16:13 +0100, Simon Riggs wrote:
> > I notice log_temp_files is a PGC_USERSET parameter, which is out of step
> > with our current thinking on who is allowed to initiate logging.
> >
> > Is there a rationale for this? Or should we set this to PGC_SUSET like
> > all the other logging functions?
>
> Patch enclosed.

Patch applied, docs updated.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +