| From: | "Alex Koh" <alexkoh(at)hotmail(dot)com> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout |
| Date: | 2004-11-02 06:31:10 |
| Message-ID: | 001801c4c0a5$8ab808b0$dd00a8c0@MCISG2 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I agree with the suggestions to attach it to userids. However, setting the
statement_timeout in the conf file is good as it will enforce everyone to
have some timeout. This will be especially useful in web applications.
Anyway, I will use ALTER USER to do it and disable statement_timeout in the
conf file.
Thanks!
Alex Koh
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, November 02, 2004 11:48 AM
To: Alex Koh
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #1302: Vacuumdb and vacuumlo should disable
statement_timeout
"PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> writes:
> IMHO vacuumdb and vacuumlo should disable statement_timeout before
vacuuming
> the database.
IMHO this request suggests that you are not setting statement_timeout in
sane places. One reasonable setup is to attach it to userids other than
the one used for vacuuming.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laferriere, Al | 2004-11-02 06:32:42 | 8.0 beta4: Exception with setBoolean on char column |
| Previous Message | Tom Lane | 2004-11-02 03:48:20 | Re: BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout |