On Thu, 19 Jun 2008, Tom Lane <[EMAIL PROTECTED]> writes:
> Volkan YAZICI <[EMAIL PROTECTED]> writes:
>> # tail -n 2 /srv/pg/pg_log/2008-06-19_141725.log
>> migration_test postgres 2008-06-19 17:58:05.185 EEST LOG: duration:
>> 2315.420 ms statement: EXECUTE foo(1000);
>> migration_test po
Volkan YAZICI wrote:
> I don't want to interrupt your work, but as far as I see from logs --
> with the configurations I sent previously -- PostgreSQL doesn't log
> parameter values for queries dropped into query duration limit. (Using
> PostgreSQL 8.3.1.) Consider this test case:
>
> test# PRE
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> PostgreSQL 8.3.1.) Consider this test case:
> test# PREPARE foo (int) AS
> ] SELECT S.i * T.i
> ] FROM generate_series(1, $1) AS S(i),
> ]generate_series(1, $1) AS T(i);
> test# EXECUTE foo (1000);
> ...
> # tail -n 2 /srv/pg/pg
On Thu, 19 Jun 2008, Tom Lane <[EMAIL PROTECTED]> writes:
> What PG version are you using? Since 8.2 log_duration should show
> parameter values.
I don't want to interrupt your work, but as far as I see from logs --
with the configurations I sent previously -- PostgreSQL doesn't log
parameter val
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> While log_statements logs parameter values with the logged queries, I
> cannot see parameter values logged for erronous queries and queries
> catched by log_min_duration_statements.
What PG version are you using? Since 8.2 log_duration should show
param
Hi,
While log_statements logs parameter values with the logged queries, I
cannot see parameter values logged for erronous queries and queries
catched by log_min_duration_statements.
Here are our logging settings:
# grep ^log postgresql.conf
logging_collector = on # Enable ca
