From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Greg Stark" <gsstark(at)mit(dot)edu> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: log_duration |
Date: | 2003-02-13 02:06:16 |
Message-ID: | GNELIHDDFBOCMGBFGEFOMEIGCFAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2003-02-13 02:17:01 | Re: location of the configuration files |
Previous Message | Larry Rosenman | 2003-02-13 01:51:38 | Re: Changing the default configuration (was Re: |