| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
| Cc: | "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, "Jan Wieck" <JanWieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SPI and CommandCounterIncrement, redux |
| Date: | 2001-11-21 14:39:23 |
| Message-ID: | 13400.1006353563@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> writes:
>> 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 ?
SPI's habit is to do CommandCounterIncrement *before* it starts a query,
rather than after. I think this makes sense, since otherwise we'd have
to do a CommandCounterIncrement at the start of every function call,
whether the function contained any subqueries or not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-21 14:53:22 | Re: internals.ps |
| Previous Message | König, Frank | 2001-11-21 14:15:22 | upper and lower doesn't work with german umlaut? |