dbTalk Databases Forums  

[BUGS] BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss [BUGS] BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
PostgreSQL Bugs List
 
Posts: n/a

Default [BUGS] BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout - 11-01-2004 , 07:30 PM







The following bug has been logged online:

Bug reference: 1302
Logged by: Alex Koh

Email address: alexkoh (AT) hotmail (DOT) com

PostgreSQL version: 7.3.2

Operating system: Linux Redhat 8

Description: Vacuumdb and vacuumlo should disable statement_timeout

Details:

IMHO vacuumdb and vacuumlo should disable statement_timeout before vacuuming
the database. This should prevent timeouts when vacuuming large tables like
pg_largeobject.


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)

Reply With Quote
  #2  
Old   
Bruce Momjian
 
Posts: n/a

Default Re: [BUGS] BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout - 11-01-2004 , 08:40 PM






PostgreSQL Bugs List wrote:
Quote:
The following bug has been logged online:

Bug reference: 1302
Logged by: Alex Koh

Email address: alexkoh (AT) hotmail (DOT) com

PostgreSQL version: 7.3.2

Operating system: Linux Redhat 8

Description: Vacuumdb and vacuumlo should disable statement_timeout

Details:

IMHO vacuumdb and vacuumlo should disable statement_timeout before vacuuming
the database. This should prevent timeouts when vacuuming large tables like
pg_largeobject.
If you have set statement_timeout globally you should expect such
problems. That parameter is primarily for per-session use or per-user
use using ALTER USER and not to be set for administrators. If you
really want a fix, use ALTER USER to turn it off for the super-user.

--
Bruce Momjian | http://candle.pha.pa.us
pgman (AT) candle (DOT) pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match


Reply With Quote
  #3  
Old   
Tom Lane
 
Posts: n/a

Default Re: [BUGS] BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout - 11-01-2004 , 10:10 PM



"PostgreSQL Bugs List" <pgsql-bugs (AT) postgresql (DOT) org> writes:
Quote:
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

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match


Reply With Quote
  #4  
Old   
Bruce Momjian
 
Posts: n/a

Default Re: [BUGS] BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout - 11-02-2004 , 09:00 AM



Alex Koh wrote:
Quote:
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.
Yep, that's how I would do it. If you want it on in the config file you
should turn it off for super-users.

--
Bruce Momjian | http://candle.pha.pa.us
pgman (AT) candle (DOT) pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org


Reply With Quote
  #5  
Old   
Alex Koh
 
Posts: n/a

Default Re: [BUGS] BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout - 11-07-2004 , 07:05 PM



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.pa.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:
Quote:
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

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.