Lists: | pgsql-docs |
---|
From: | gabrielle <gorthx(at)gmail(dot)com> |
---|---|
To: | pgsql-docs(at)postgresql(dot)org |
Subject: | [PATCH] log_statement docs |
Date: | 2010-02-25 02:42:19 |
Message-ID: | 48bb92b1002241842h2ee4cc38pf2aee19f3071273e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-docs |
Patch amends description of log_statement to include definition of "all" option.
gabrielle
Attachment | Content-Type | Size |
---|---|---|
log_statement.patch | text/x-patch | 1.1 KB |
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | gabrielle <gorthx(at)gmail(dot)com> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [PATCH] log_statement docs |
Date: | 2010-02-25 03:14:57 |
Message-ID: | 18812.1267067697@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-docs |
gabrielle <gorthx(at)gmail(dot)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
From: | gabrielle <gorthx(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [PATCH] log_statement docs |
Date: | 2010-02-25 17:21:46 |
Message-ID: | 48bb92b1002250921k3a1ae0a0xab26038ccaae089d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-docs |
On Wed, Feb 24, 2010 at 7:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> gabrielle <gorthx(at)gmail(dot)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
From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | gabrielle <gorthx(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [PATCH] log_statement docs |
Date: | 2010-02-25 18:47:03 |
Message-ID: | 201002251847.o1PIl3h23647@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-docs |
gabrielle wrote:
> On Wed, Feb 24, 2010 at 7:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > gabrielle <gorthx(at)gmail(dot)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(at)momjian(dot)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. +
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | gabrielle <gorthx(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [PATCH] log_statement docs |
Date: | 2010-02-25 19:07:57 |
Message-ID: | 7494.1267124877@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-docs |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> gabrielle wrote:
>> On Wed, Feb 24, 2010 at 7:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | gabrielle <gorthx(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [PATCH] log_statement docs |
Date: | 2010-02-25 19:20:41 |
Message-ID: | 201002251920.o1PJKfM01351@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-docs |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > gabrielle wrote:
> >> On Wed, Feb 24, 2010 at 7:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(at)momjian(dot)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. +
Attachment | Content-Type | Size |
---|---|---|
/rtmp/diff | text/x-diff | 1.3 KB |
From: | gabrielle <gorthx(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [PATCH] log_statement docs |
Date: | 2010-02-25 19:27:37 |
Message-ID: | 48bb92b1002251127g7e505dcfy5e30089d43d6a0c8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-docs |
On Thu, Feb 25, 2010 at 11:20 AM, Bruce Momjian <bruce(at)momjian(dot)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