Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block
Date
Msg-id CA+TgmoagqbUsXRrf3T124dpyt4dPwzpe8x84i-p1iN5mfkX-gw@mail.gmail.com
Whole thread Raw
In response to Suggestion: Issue warning when calling SET TRANSACTION outside transaction block  (Morten Hustveit <morten@eventures.vc>)
Responses Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block  (Amit kapila <amit.kapila@huawei.com>)
List pgsql-hackers
On Fri, Feb 1, 2013 at 12:04 AM, Amit Kapila <amit.kapila@huawei.com> wrote:
> I think user should be aware of effect before using SET commands, as these are used at various levels (TRANSACTION,
SESSION,...).
 

Ideally, sure.  But these kinds of mistakes are easy to make.  That's
why LOCK and DECLARE CURSOR already emit errors in this case - why
should this one be any different?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: GetOldestXmin going backwards is dangerous after all
Next
From: Robert Haas
Date:
Subject: Re: autovacuum not prioritising for-wraparound tables