Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
Cc: Morten Hustveit <morten(at)eventures(dot)vc>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block
Date: 2013-02-02 15:38:16
Message-ID: CA+TgmoagqbUsXRrf3T124dpyt4dPwzpe8x84i-p1iN5mfkX-gw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 1, 2013 at 12:04 AM, Amit Kapila <amit(dot)kapila(at)huawei(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-02-02 15:43:43 Re: autovacuum not prioritising for-wraparound tables
Previous Message Robert Haas 2013-02-02 15:34:43 Re: GetOldestXmin going backwards is dangerous after all