Skip site navigation (1) Skip section navigation (2)

Re: postgres crash on CURSORS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postgres crash on CURSORS
Date: 2000-04-06 21:42:31
Message-ID: 28930.955057351@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
>> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>>>>> If we are in abort state and
>>>>> the submitted query string is
>>>>> 
>>>>> SELECT foo ; ROLLBACK ; SELECT bar
>>>>> 
>>>>> it seems to me that the correct response is to reject the first select
>>>>> and process the second.

> Unfortunately I've never used multiple query and understand
> little about it. For example,how to know using libpq that the first
> select was ignored ?

If you use PQexec then you can't really tell, because you'll only get
back the last command's result.  If you use PQsendQuery/PQgetResult
then you'll get back multiple PGresults from a multi-query string, and
you can examine each one to see if it was executed or not.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Hiroshi InoueDate: 2000-04-06 23:38:41
Subject: RE: 7.0 like selectivity
Previous:From: Tom LaneDate: 2000-04-06 20:35:00
Subject: Re: 'on insert' rules and defaults

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group