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

Re: BUG #1592: "with hold" cursor problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: andrew(at)supernews(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1592: "with hold" cursor problem
Date: 2005-04-11 16:46:17
Message-ID: 2668.1113237977@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> One further question is if it's right for the holdable portal to fire
> trigger at transaction commit.  ISTM the non-surprising answer would be
> for them to fire at FETCH time.  (But of course this is hard to
> implement, since at that time we don't have executor machinery ...)

Our definition of a holdable cursor is that the query execution is
completed during transaction commit, and all you have left after that
is a static image of the results.  So it's consistent to fire any
associated triggers during commit, too.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Eric McGoughDate: 2005-04-11 16:50:11
Subject: Re: BUG #1582: boolean DEFAULT TRUE results in FALSE for NULL values
Previous:From: Alvaro HerreraDate: 2005-04-11 16:37:38
Subject: Re: BUG #1592: "with hold" cursor problem

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