From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Parser abort ignoring following commands |
Date: | 2001-05-26 15:31:28 |
Message-ID: | Pine.LNX.4.30.0105261721400.757-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane writes:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > psql -c 'select * from pg_class; select * from no_such_table;'
> > Shouldn't this at least give me the result of the first select before
> > aborting the second?
>
> The behavior you are complaining of is not the backend's fault.
> The reason it acts that way is that psql is feeding the entire -c
> string to the backend as one query, and not paying any attention
> to the possibility that multiple query results might be available
> from the string.
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.
$ psql -c 'drop user joe; drop user foo;'
ERROR: DROP USER: user "foo" does not exist
User "joe" exists, but it is not dropped.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-05-26 15:36:54 | Re: Parser abort ignoring following commands |
Previous Message | Tom Lane | 2001-05-26 15:12:31 | Re: Parser abort ignoring following commands |