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

RE: postgres crash on CURSORS

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 01:37:14
Message-ID: 000501bf9f68$a2d5d0c0$2801007e@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
> -----Original Message-----
> 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.  The currently committed code does so, but
> >> your patch would fail.
> 
> > It seems pg_parse_and_plan() returns NIL plan_list and NIL
> > querytree_list in this case.
> 
> You're not looking at current CVS ;-)
>

Sorry,I see your change now.

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 ?

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp 

In response to

Responses

pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2000-04-06 01:58:06
Subject: Re: [HACKERS] Doc updates
Previous:From: Bruce MomjianDate: 2000-04-06 01:24:26
Subject: Re: Index tuple count != heap tuple count problem identified]

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