On Fri, Aug 19, 2011 at 3:31 PM, Tom Lane wrote:
>> As for ROLLBACK, I think it should chuck an error instead of doing
>> this funny
>> emit-a-warning-and-silently-arrange-for-the-transaction-to-be-aborted-later
>> thing.
>
> I'm pretty unexcited about changing the behavior of established
> mains
Robert Haas writes:
> I spent some time looking at this afternoon and it appears that the
> root of this problem is that we're a bit schizophrenic about whether a
> multi-query command string constitutes a transaction or not.
Yeah. The current behavior sort of automatically adds a BEGIN and a
CO
On Thu, Aug 18, 2011 at 3:57 AM, Marcin Mańk wrote:
> On Wed, Aug 17, 2011 at 11:30 PM, Tom Lane wrote:
>> =?UTF-8?B?TWFyY2luIE1hxYRr?= writes:
>>> psql -c 'release q; prepare q(int) as select 1'
>>> FATAL: ReleaseSavepoint: unexpected state STARTED
>>
>> Can't get terribly excited about that,
On Wed, Aug 17, 2011 at 11:30 PM, Tom Lane wrote:
> =?UTF-8?B?TWFyY2luIE1hxYRr?= writes:
>> psql -c 'release q; prepare q(int) as select 1'
>> FATAL: ReleaseSavepoint: unexpected state STARTED
>
> Can't get terribly excited about that, seeing that the statement is
> surely going to draw an erro
=?UTF-8?B?TWFyY2luIE1hxYRr?= writes:
> psql -c 'release q; prepare q(int) as select 1'
> FATAL: ReleaseSavepoint: unexpected state STARTED
Can't get terribly excited about that, seeing that the statement is
surely going to draw an error and abort processing the rest of the
command string in any
Hello
I tried reporting the following bug via web form, it somerhow got lost
(it is not in pgsql-bugs archives, it was #6157 I believe). Anyway,
here it is:
psql -c 'release q; prepare q(int) as select 1'
FATAL: ReleaseSavepoint: unexpected state STARTED
server closed the connection unexpectedl
