Re: SPI and CommandCounterIncrement, redux

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, "Jan Wieck" <JanWieck(at)Yahoo(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SPI and CommandCounterIncrement, redux
Date: 2001-11-21 09:06:47
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA41EB426@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Note the failure to display "Name :: name4". The problem is that
> no CommandCounterIncrement happens between the second INSERT and
> the FOR ... SELECT, so the inserted row is considered not yet visible.

I wonder why the insert does not do the CommandCounterIncrement,
since it is a statement that did modification and all subsequent
statements should see the effect ?
In other places this is the usual practice (CommandCounterIncrement
after
modification), no ?
Or is this a stupid question.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2001-11-21 09:27:24 Re: ecpg+AIX 5L compile failure with current
Previous Message Karel Zak 2001-11-21 08:23:44 Re: broken time operator?