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 |
Thread: | |
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 | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-02-25 19:07:57 | Re: [PATCH] log_statement docs |
Previous Message | gabrielle | 2010-02-25 17:21:46 | Re: [PATCH] log_statement docs |