Re: use log_statement to log only SELECTs?

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Brian Witt <bwitt(at)bart(dot)gov>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: use log_statement to log only SELECTs?
Date: 2009-12-03 00:24:58
Message-ID: 4B17055A.3020506@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Brian Witt wrote:
> Thanks for the response. I was afraid of that. Can I make this a
> feature request? How do I do that? Should I add it to this page:
> http://wiki.postgresql.org/wiki/Todo
>
Generally it's better to see if there's at least some general support
for an idea before adding it to the TODO list. In this case, I don't
think you'll find any. The current way you get everything out of
log_statement is completely reasonable for most people, and I doubt
you'll ever get one of the folks who hack on PostgreSQL to work on the
feature you'd like unless you paid them to. You'd need a much better
justification for why you can't just filter things out of the log
yourself before it would be worth further complicating the code
involved. It's just not a common request--if anything, you might find
people want everything *but* SELECTs.

--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2009-12-03 00:29:49 Re: using querys like: 'select table.*'
Previous Message Daniel 2009-12-03 00:16:07 Strange. I can logon with an invalid or no password atall