Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= <[EMAIL PROTECTED]> writes:
> On Wed, 2008-11-19 at 13:54 +, Grzegorz JaÅkiewicz wrote:
>> change loging level to debug1 in postgresql.conf, it will log
>> statements.
> Why not just setting log_statement to all? (or whatever)
I think the least verbose way
On Wed, Nov 19, 2008 at 3:51 PM, Devrim GÜNDÜZ <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-11-19 at 13:54 +, Grzegorz Jaśkiewicz wrote:
> > change loging level to debug1 in postgresql.conf, it will log
> > statements.
>
> Why not just setting log_statement to all? (or whatever)
there's probabl
On Wed, 2008-11-19 at 13:54 +, Grzegorz Jaśkiewicz wrote:
> change loging level to debug1 in postgresql.conf, it will log
> statements.
Why not just setting log_statement to all? (or whatever)
--
Devrim GÜNDÜZ, RHCE
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
change loging level to debug1 in postgresql.conf, it will log statements.
you don't have to reboot postgres for that - just reload it (either pg_ctl
reload - as opstgres user, or /etc/init.d/postgres reload).
I can't find what's the statement causing this warning:
2008-11-19 14:45:34 CET WARNING: nonstandard use of \\ in a string
literal at character 32 2008-11-19 14:45:34 CET HINT: Use the
escape string syntax for backslashes, e.g., E'\\'.
I mean... I know how to fix it... but how can I find the st
