Thread: use log_statement to log only SELECTs?

Hi,

I've been looking for a way to use log_statement to log only select
statements; is this possible?  (I'm using PostgreSQL 8.1.18)

I'd like to know if someone tried to read the data back from the
database, but don't care to see the inserts or updates since these may
have sensitive data like credit card data which I don't want logged in
the logs.  I really don't even care if the SELECT was successful or not,
or what the results of the SELECT were.

Thanks,
Brian

Brian Witt wrote:
> Hi,
>
> I've been looking for a way to use log_statement to log only select
> statements; is this possible?  (I'm using PostgreSQL 8.1.18)
>
> I'd like to know if someone tried to read the data back from the
> database, but don't care to see the inserts or updates since these may
> have sensitive data like credit card data which I don't want logged in
> the logs.  I really don't even care if the SELECT was successful or not,
> or what the results of the SELECT were.

No, log_statement doesn't allow do that, and I can't think of another
option.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

On Sun, 2009-11-29 at 06:00 -0500, Bruce Momjian wrote:

> Brian Witt wrote:
> > I've been looking for a way to use log_statement to log only select
> > statements; is this possible?  (I'm using PostgreSQL 8.1.18)

> No, log_statement doesn't allow do that, and I can't think of another
> option.

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

Thanks again,
Brian

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@2ndQuadrant.com  www.2ndQuadrant.com