From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ang Chin Han <angch@bytecraft.com.my>
Cc: Oliver Elphick <olly@lfix.co.uk>
Cc: Szabó Péter <matyee@westel900.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Lock!
Date: Wed, 15 Oct 2003 11:26:52 -0400
Message-ID: <15774.1066231612@sss.pgh.pa.us> (raw)
In-Reply-To: <3F8CCC7F.6@bytecraft.com.my>
References: <004c01c39175$0f0b3620$2702a8c0@WorkGroup>
<1066148873.5581.67.camel@linda.lfix.co.uk>
<3F8CCC7F.6@bytecraft.com.my>
Ang Chin Han <angch@bytecraft.com.my> writes:
> Just remember to reset STATEMENT_TIMEOUT to zero or your default before
> any slow queries in that transaction.
Also, you can use "SET LOCAL ..." to constrain the effects of the SET
command; this is probably safer than trying to remember to reset the
variable when you're done.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, angch@bytecraft.com.my, olly@lfix.co.uk, matyee@westel900.net
Subject: Re: Lock!
In-Reply-To: <15774.1066231612@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox