Re: SPI and CommandCounterIncrement, redux - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: SPI and CommandCounterIncrement, redux
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA41EB426@m0114.s-mxs.net
Whole thread Raw
In response to SPI and CommandCounterIncrement, redux  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SPI and CommandCounterIncrement, redux
List 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


pgsql-hackers by date:

Previous
From: Karel Zak
Date:
Subject: Re: broken time operator?
Next
From: Michael Meskes
Date:
Subject: Re: ecpg+AIX 5L compile failure with current