[PATCH] log_statement docs

Started by gabrielleabout 16 years ago7 messagesdocs
Jump to latest
#1gabrielle
gorthx@gmail.com

Patch amends description of log_statement to include definition of "all" option.

gabrielle

Attachments:

log_statement.patchtext/x-patch; charset=US-ASCII; name=log_statement.patchDownload+3-3
#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: gabrielle (#1)
Re: [PATCH] log_statement docs

gabrielle <gorthx@gmail.com> writes:

Patch amends description of log_statement to include definition of "all" option.

Shouldn't it just say "all means all", if we think that needs to be
explained?

regards, tom lane

#3gabrielle
gorthx@gmail.com
In reply to: Tom Lane (#2)
Re: [PATCH] log_statement docs

On Wed, Feb 24, 2010 at 7:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

gabrielle <gorthx@gmail.com> writes:

Patch amends description of log_statement to include definition of "all" option.

Shouldn't it just say "all means all", if we think that needs to be
explained?

I think it should say something about the "all" option. I read &
re-read that section trying to figure out what the difference between
"mod" and "all" was, and finally asked on the irc channel. As it
stands, it essentially says "there are three options to this command,
but we're only going to tell you about two of them." :)

Thanks!
gabrielle

#4Bruce Momjian
bruce@momjian.us
In reply to: gabrielle (#3)
Re: [PATCH] log_statement docs

gabrielle wrote:

On Wed, Feb 24, 2010 at 7:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

gabrielle <gorthx@gmail.com> writes:

Patch amends description of log_statement to include definition of "all" option.

Shouldn't it just say "all means all", if we think that needs to be
explained?

I think it should say something about the "all" option. I read &
re-read that section trying to figure out what the difference between
"mod" and "all" was, and finally asked on the irc channel. As it
stands, it essentially says "there are three options to this command,
but we're only going to tell you about two of them." :)

Well, if you take a look at utility.c:GetCommandLogLevel() you will see
that ALL includes a lot more commands than just SELECT.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com
  PG East:  http://www.enterprisedb.com/community/nav-pg-east-2010.do
  + If your life is a hard drive, Christ can be your backup. +
#5Tom Lane
tgl@sss.pgh.pa.us
In reply to: Bruce Momjian (#4)
Re: [PATCH] log_statement docs

Bruce Momjian <bruce@momjian.us> writes:

gabrielle wrote:

On Wed, Feb 24, 2010 at 7:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Shouldn't it just say "all means all", if we think that needs to be
explained?

I think it should say something about the "all" option. I read &
re-read that section trying to figure out what the difference between
"mod" and "all" was, and finally asked on the irc channel. As it
stands, it essentially says "there are three options to this command,
but we're only going to tell you about two of them." :)

Well, if you take a look at utility.c:GetCommandLogLevel() you will see
that ALL includes a lot more commands than just SELECT.

Yeah. My objection was not to documenting ALL, it was to documenting it
with exactly that sentence, which seems both needlessly complicated and
subject to errors of omission.

regards, tom lane

#6Bruce Momjian
bruce@momjian.us
In reply to: Tom Lane (#5)
Re: [PATCH] log_statement docs

Tom Lane wrote:

Bruce Momjian <bruce@momjian.us> writes:

gabrielle wrote:

On Wed, Feb 24, 2010 at 7:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Shouldn't it just say "all means all", if we think that needs to be
explained?

I think it should say something about the "all" option. I read &
re-read that section trying to figure out what the difference between
"mod" and "all" was, and finally asked on the irc channel. As it
stands, it essentially says "there are three options to this command,
but we're only going to tell you about two of them." :)

Well, if you take a look at utility.c:GetCommandLogLevel() you will see
that ALL includes a lot more commands than just SELECT.

Yeah. My objection was not to documenting ALL, it was to documenting it
with exactly that sentence, which seems both needlessly complicated and
subject to errors of omission.

I have applied the following patch with adds "off" and "all statements"
identifiers. This is probaby the right level of detail for this.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com
  PG East:  http://www.enterprisedb.com/community/nav-pg-east-2010.do
  + If your life is a hard drive, Christ can be your backup. +

Attachments:

/rtmp/difftext/x-diffDownload+4-4
#7gabrielle
gorthx@gmail.com
In reply to: Bruce Momjian (#6)
Re: [PATCH] log_statement docs

On Thu, Feb 25, 2010 at 11:20 AM, Bruce Momjian <bruce@momjian.us> wrote:

I have applied the following patch with adds "off" and "all statements"
identifiers.  This is probaby the right level of detail for this.

Thank you!

gabrielle