![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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. |
#3
| |||
| |||
|
|
IMHO vacuumdb and vacuumlo should disable statement_timeout before vacuuming the database. |
#4
| |||
| |||
|
|
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. |
#5
| |||
| |||
|
|
IMHO vacuumdb and vacuumlo should disable statement_timeout before vacuuming the database. |
![]() |
| Thread Tools | |
| Display Modes | |
| |