From: | Jerry Sievers <jerry(at)jerrysievers(dot)com> |
---|---|
To: | Marcin Mañk <marcin(dot)mank(at)gmail(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: statement_timeout |
Date: | 2006-11-16 18:44:03 |
Message-ID: | m3zmarp6z0.fsf@homie.jerrysievers.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Marcin Mañk <marcin(dot)mank(at)gmail(dot)com> writes:
> Hello.
> I have an unconfirmed feeling that autovac does not like system-wide
> statement_timeout. I.e. when I in some panic move set system-wide
> statement_timeout to 90 seconds, autovac stopped working (I do not know for
> 100% if there is a dependency).
>
> Ups... Now I checked that pg_dump has the same issue. and vacuumdb. This is
> all on 8.1.4 .
>
> Yeah, system-wide statement_timeout is not much of a brilliant idea :(
Ok so why don't you exempt user postgres and/or any other roles known
to run lengthy jobs?
alter role postgres set statement_timeout to 0;
> Pozdrawiam
> Marcin Mañk
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org/
>
--
-------------------------------------------------------------------------------
Jerry Sievers 305 854-3001 (home) Production Database Administrator
305 321-1144 (mobil WWW E-Commerce Consultant
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2006-11-16 18:47:48 | Re: Why the data changes it's value by itself! |
Previous Message | Richard Huxton | 2006-11-16 18:42:36 | Re: Partial index |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-11-16 18:50:00 | Re: statement_timeout |
Previous Message | Tom Lane | 2006-11-16 18:43:26 | Re: Custom Data Type Question |