Userset logging

Started by Simon Riggsalmost 18 years ago3 messageshackers
Jump to latest
#1Simon Riggs
simon@2ndQuadrant.com

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

#2Simon Riggs
simon@2ndQuadrant.com
In reply to: Simon Riggs (#1)
Re: [HACKERS] Userset logging

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

Attachments:

log_temp_files_suset.v1.patchtext/x-patch; charset=UTF-8; name=log_temp_files_suset.v1.patchDownload+2-2
#3Bruce Momjian
bruce@momjian.us
In reply to: Simon Riggs (#2)
Re: [HACKERS] Userset logging

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@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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