From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: compiling client utils under win32 - current 7.3devel |
Date: | 2002-09-26 02:11:48 |
Message-ID: | 200209260211.g8Q2Bm125991@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-26 03:15:12 | Re: Insert Performance |
Previous Message | Bruce Momjian | 2002-09-26 02:07:17 | Re: postmaster -d option (was Re: [GENERAL] Relation 0 does not exist) |