| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
| Cc: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>, Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: tracking down a warning |
| Date: | 2008-11-19 18:28:55 |
| Message-ID: | 13969.1227119335@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= <devrim(at)gunduz(dot)org> writes:
> On Wed, 2008-11-19 at 13:54 +0000, Grzegorz Jakiewicz 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 to find it would be to set
log_min_error_statement to "warning". With either of the above
you'd get lots of useless log traffic about non-problematic statements.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-11-19 19:15:20 | Re: Any risks in using FUNCTIONs (stored procedures) instead of raw sql queries? |
| Previous Message | Josh Harrison | 2008-11-19 18:23:59 | Re: PostgreSQL 8.4 download? |