On Mon, Mar 29, 2010 at 8:33 PM, Jun Wang wrote:
> Hi,
>
> I try to set the statement_timeout so that "select pg_stop_backup();"
> will not hang if archive command failed. Below are the command and
> errors.
>
Try it by putting the commands in a file and running it like
psql . -f mysqlfile.s
Hi,
I try to set the statement_timeout so that "select pg_stop_backup();"
will not hang if archive command failed. Below are the command and
Can somebody help on this?
Thanks.
* From: Ju
Hi,
I try to set the statement_timeout so that "select pg_stop_backup();"
will not hang if archive command failed. Below are the command and
errors.
psql.exe" -d mydb -h myhost -p 5432 -U postgres -w -c "set
statement_timeout = 1000; select pg_stop_backup();"
WARNING: pg_stop_backup still waitin
I have a problem with fetching from cursors sometimes taking an
extremely long time to run. I am attempting to use the
statement_timeout parameter to limit the runtime on these.
PostgreSQL 8.2.4
Linux 2.6.22.14-72.fc6 #1 SMP Wed Nov 21 13:44:07 EST 2007 i686 i686
i386 GNU/Linux
begin;
set searc
andy rost <[EMAIL PROTECTED]> writes:
> No big deal. We simply modified the cron job to:
> set statement_timeout=0; VACUUM ANALYZE VERBOSE;
> Should work, right?
> Now we get the following entries in our log files:
> 2006-11-30 00:03:31 CST ERROR: canceling statement due to statement timeout
> 2
We run VACUUM ANALYZE as a cron job on PostgreSQL v8.1.3 on an Opteron
box running FreeBSD 6.0-RELEASE #10. We set statement_timeout to 720
in postgresql.conf. Since this task often takes longer than two hours we
encounter the following messages in our log files:
2006-11-30 00:03:31 CST ER
