Re: log_duration - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: log_duration
Date
Msg-id GNELIHDDFBOCMGBFGEFOMEIGCFAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: log_duration  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: log_duration
Re: [HACKERS] log_duration
Re: [HACKERS] log_duration
List pgsql-hackers
> Tom is right here.  log_duration _just_ prints the duration, so we would
> need to basically create a merged param that does log_duration and
> log_statement and have it activate only if the statement takes more than
> X milliseconds, something like log_long_statement, or something like
> that.
>
> Here are the log_* params we have:
>
>     log_connections = false
>     log_hostname = false
>     log_source_port = false
>     log_pid = false
>     log_statement = false
>     log_duration = false
>     log_timestamp = false

OK, while I'm doing all this benchmarking and stuff - is there any sort of
option where I can see it logged when a sort doesn't have enought sort
memory and hence hits the disk?  eg. an elog(LOG) is emitted?

Chris



pgsql-hackers by date:

Previous
From: Larry Rosenman
Date:
Subject: Re: Changing the default configuration (was Re:
Next
From: Rod Taylor
Date:
Subject: Re: location of the configuration files