Peter Eisentraut wrote:
> Tom Lane writes:
> > Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > > No, I think there is another problem. How about something without
> > > selects:
> > > $ psql -c 'delete from pk; delete from xx;'
> > > ERROR: Relation 'xx' does not exist
> > > "pk" exists, but nothing is deleted.
> > 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().
I guess that this is a multi-command statement ?
It has always been so, except that psql seems to do some parsing and
each command to backend separately.
In response to
pgsql-hackers by date
|Next:||From: Adam Haberlach||Date: 2001-05-27 02:00:44|
|Subject: Re: Parser abort ignoring following commands|
|Previous:||From: Oleg Bartunov||Date: 2001-05-26 17:53:39|
|Subject: Re: First version of multi-key index support for GiST|