Skip site navigation (1) Skip section navigation (2)

Re: [PATCH] log_statement docs

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 (view raw or flat)
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. +

In response to

Responses

pgsql-docs by date

Next:From: Tom LaneDate: 2010-02-25 19:07:57
Subject: Re: [PATCH] log_statement docs
Previous:From: gabrielleDate: 2010-02-25 17:21:46
Subject: Re: [PATCH] log_statement docs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group