Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout - Mailing list pgsql-bugs

From Alex Koh
Subject Re: BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout
Date
Msg-id 001801c4c0a5$8ab808b0$dd00a8c0@MCISG2
Whole thread Raw
In response to Re: BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
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@sss.pgh.pa.us]
Sent: Tuesday, November 02, 2004 11:48 AM
To: Alex Koh
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #1302: Vacuumdb and vacuumlo should disable
statement_timeout

"PostgreSQL Bugs List" <pgsql-bugs@postgresql.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

pgsql-bugs by date:

Previous
From: "Laferriere, Al"
Date:
Subject: 8.0 beta4: Exception with setBoolean on char column
Next
From: "Laferriere, Al"
Date:
Subject: Re: 8.0 beta4: Exception when including catalog qualifier in SELECT from