Re: log_min_duration_statement oddity

Well, I'm completely sure that long running queries from local
connections are logged, as I can see them in the log file. Quick queries
are not logged even for local connections, I tested that too...
And I'm also sure that I do have long running queries on remote
connections, our application logged some really long running ones.

Now the remote connections are coming from Java (the JDBC driver), and I
guess it could be that java is setting log_min_duration_statement - I
was not aware that this is possible. It would be strange though, why
would the JDBC driver set something like this ? Or user specific setting
means something completely different ? (I confess I have no idea how can
you make user specific settings, or data base specific settings for that
matter). In any case, I did not deliberately make any separate settings
per data base or per user, and nobody else is messing with postgres
settings here...

Thanks,
Csaba.

On Wed, 2005-10-19 at 17:46, Tom Lane wrote:
> Csaba Nagy <nagy(at)ecircle-ag(dot)com> writes:
> > I wonder if I understood correctly what log_min_duration_statement
> > does... I set it to 2000, and the result is that all queries running
> > more than 2 seconds on _local_ connections are logged, but long running
> > queries on remote connections are not logged.
>
> I can't reproduce that. Sure you've diagnosed the problem correctly?
> It seems highly unlikely that the source of the connection would have
> anything to do with it. User or database could (eg, perhaps there's
> a user-specific setting of log_min_duration_statement).
>
> regards, tom lane