Re: statement_timeout

From: Casey Duncan <casey(at)pandora(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:38:56
Message-ID: 43895C5C-318B-4F44-A6FC-0B1E833D323D@pandora.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

When I configure statement_timeout globally, I typically override it
for superusers and other accounts used by dbas. Just issue:

ALTER USER postgres SET statement_timeout = 0;

Repeat for other superusers (slony, etc). Then the policy won't apply
to them.

-Casey

On Nov 16, 2006, at 6:46 AM, Marcin Mańk wrote:

> 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 :(
>
> Pozdrawiam
> Marcin Mańk
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Danilo Freitas da Costa 2006-11-16 18:41:13 SPI
Previous Message Tom Lane 2006-11-16 18:32:09 Re: Strange Postgresql crash

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-11-16 18:43:26 Re: Custom Data Type Question
Previous Message Bruce Momjian 2006-11-16 18:35:04 Re: replication docs: split single vs. multi-master