Re: [ADMIN] log_duration / log_min_duration_statement differences between 8.1.8 and 8.2.4

2007-09-29 Thread Bruce Momjian
[EMAIL PROTECTED] wrote: > Hi, > > We're starting to migrate from postgres 8.1.8 to 8.2.4 > and noticing behavioral differences in what they log (via syslog to > /var/log/pgsql) > > The behavior we have on 8.1.8 is: > * log all data-modification queries (with duration) > * log all queries that t

[ADMIN] log_duration / log_min_duration_statement differences between 8.1.8 and 8.2.4

2007-09-26 Thread scottb
Hi, We're starting to migrate from postgres 8.1.8 to 8.2.4 and noticing behavioral differences in what they log (via syslog to /var/log/pgsql) The behavior we have on 8.1.8 is: * log all data-modification queries (with duration) * log all queries that take longer than 1000 millisec (with duratio

Re: [ADMIN] log_duration?

2007-02-19 Thread Tom Lane
Ray Stell <[EMAIL PROTECTED]> writes: > I toggle log_duration: > wiki=# \!date > Mon Feb 19 11:14:35 EST 2007 > wiki=# set log_duration=off; > SET SET only affects your own session, not anyone else's ... regards, tom lane ---(end of broadcast)---

Re: [ADMIN] log_duration?

2007-02-19 Thread Andy Shellam (Mailing Lists)
Ray Stell wrote: I toggle log_duration: wiki=# \!date Mon Feb 19 11:14:35 EST 2007 wiki=# set log_duration=off; SET wiki=# SELECT current_setting('log_duration'); current_setting - off (1 row) yet duration continues to be logged: wiki,13190,wiki,2007-02-19 11:16:00.926 EST,4

[ADMIN] log_duration?

2007-02-19 Thread Ray Stell
I toggle log_duration: wiki=# \!date Mon Feb 19 11:14:35 EST 2007 wiki=# set log_duration=off; SET wiki=# SELECT current_setting('log_duration'); current_setting - off (1 row) yet duration continues to be logged: wiki,13190,wiki,2007-02-19 11:16:00.926 EST,45d94f9e.3386,36108

Re: [ADMIN] log_duration

2005-02-07 Thread Simon Riggs
>Tom Lane > "Simon Riggs" <[EMAIL PROTECTED]> writes: > > Further update on this: > > > We've isolated this issue to JDBC client access. > > Ah-hah, now it makes sense. I believe the JDBC driver always uses > extended query protocol (parse/bind/execute messages). Thanks for the *solution. I had

Re: [ADMIN] log_duration

2005-02-06 Thread Tom Lane
"Simon Riggs" <[EMAIL PROTECTED]> writes: > Further update on this: > We've isolated this issue to JDBC client access. Ah-hah, now it makes sense. I believe the JDBC driver always uses extended query protocol (parse/bind/execute messages). We know that that code path is a bit shy of a load with

Re: [ADMIN] log_duration

2005-02-05 Thread Simon Riggs
>Simon Riggs > > From: Tom Lane > > "Simon Riggs" <[EMAIL PROTECTED]> writes: > > > On top of a confusing day, I now have this: > > > I set log_duration = true in a postgresql.conf file. > > > I startup and test, local users connected via psql: > > working, no problem. > > > Users connecting remote

Re: [ADMIN] log_duration

2005-02-04 Thread Simon Riggs
> From: Tom Lane > "Simon Riggs" <[EMAIL PROTECTED]> writes: > > On top of a confusing day, I now have this: > > I set log_duration = true in a postgresql.conf file. > > I startup and test, local users connected via psql: > working, no problem. > > Users connecting remotely, same user, same databas

Re: [ADMIN] log_duration

2005-02-04 Thread Tom Lane
"Simon Riggs" <[EMAIL PROTECTED]> writes: > On top of a confusing day, I now have this: > I set log_duration = true in a postgresql.conf file. > I startup and test, local users connected via psql: working, no problem. > Users connecting remotely, same user, same database: no log of query > statemen

[ADMIN] log_duration

2005-02-04 Thread Simon Riggs
On top of a confusing day, I now have this: I set log_duration = true in a postgresql.conf file. I startup and test, local users connected via psql: working, no problem. Users connecting remotely, same user, same database: no log of query statement durations. There is nothing in the code that s