Re: Parser abort ignoring following commands

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parser abort ignoring following commands
Date: 2001-05-26 16:14:52
Message-ID: 22735.990893692@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> Sure, because the transaction is rolled back. The whole string
>> is executed in one transaction. You will definitely break existing
>> applications if you change that.

> Applications that rely on this behaviour are broken. It was always said
> that statements are in their own transaction block unless in an explicit
> BEGIN/COMMIT block. A statement is defined to end at the semicolon, not
> at the end of the string you submit to PQexec().

Au contraire: single query strings have always been executed as single
transactions. Whether that would be the most consistent behavior in a
green field is quite irrelevant. We *cannot* change it now, or we will
break existing applications --- silently.

If you can find something in the documentation that states what you
claim is the definition, I'll gladly change it ;-).

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2001-05-26 17:53:39 Re: First version of multi-key index support for GiST
Previous Message Peter Eisentraut 2001-05-26 15:57:16 Re: Parser abort ignoring following commands