Re: New PostgrSQL Errors

From: Dror Matalon <dror(at)zapatec(dot)com>
To: Postgres <sfpug(at)postgresql(dot)org>
Subject: Re: New PostgrSQL Errors
Date: 2004-03-19 06:13:07
Message-ID: 20040319061307.GG1757@rlx11.zapatec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: sfpug

On Thu, Mar 18, 2004 at 08:43:39PM -0800, David Wheeler wrote:
> On Mar 18, 2004, at 5:14 PM, Dror Matalon wrote:
>
> >If you want to be explicit about this, you can set
> >log_statement = true
> >
> >which will log *every* statement that postgress sees.
>
> Ah, that's very handy, thanks. I think I might use that for profiling
> one of these days.

Actually for profiling there's another trick.

turn off the above and turn on:
log_min_duration_statement = 2500 # Log all statements whose
This will show you only statement that run for longer than 2.5 seconds.
>
> But in the meantime, once I set this, I noticed that Bricolage was
> doing a couple of queries at server startup time. This is a bad idea,
> because if DBI caches them before Apache forks, they could get screwed
> up.
>
> I've removed the queries that were running at startup time, and now it
> look looks like it might be working.
>
> Thanks for the help!
>
> Regards,
>
> David
>

--
Dror Matalon
Zapatec Inc
1700 MLK Way
Berkeley, CA 94709
http://www.fastbuzz.com
http://www.zapatec.com

In response to

Responses

Browse sfpug by date

  From Date Subject
Next Message David Wheeler 2004-03-19 06:45:21 Re: New PostgrSQL Errors
Previous Message David Wheeler 2004-03-19 04:43:39 Re: New PostgrSQL Errors