Joe Conway wrote:
> I was working with this approach, when I noticed on *unmodified* cvs tip
> (about a day old):
>
> test=# set statement_timeout=1;
> SET
> test=# \dt
> ERROR: Query was cancelled.
> test=#
>
> At:
> http://developer.postgresql.org/docs/postgres/runtime-config.html#LOGGING
> the setting is described like this:
>
> "STATEMENT_TIMEOUT (integer)
>
> Aborts any statement that takes over the specified number of milliseconds. A
> value of zero turns off the timer."
>
> The proposed change will take this to a 1 second granularity anyway, so I was
> thinking we should change the setting to have a UOM of seconds, and fix the
> documentation. Any comments or concerns with regard to this plan?
Uh, I thought you were changing connection_timeout, which is libpq and
not a GUC parameter, not statement_timeout. Do we want sub-second
timeout values? Not sure.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073
