> A SELECT ... FROM "othertable" ... FOR SHARE won't conflict with a
> concurrent update on "atable".
>
> Do I guess right that there was also an UPDATE on the row in
> "othertable"?
Yes, that was what I meant to convey. Sorry if I was not clear. The
point was that an INSERT to "atable" conflicte
Peter Schuller wrote:
> Using PostgreSQL 8.2, I have "atable" one of whose columns reference a
> column in "othertable". I see serialization failures as a result of
> *inserts* to atable in the context of:
>
> '"SELECT 1 FROM ONLY othertable x WHERE "otherid" = $1 FOR SHARE OF
> x" ' in 'INSER
Hello,
Using PostgreSQL 8.2, I have "atable" one of whose columns reference a
column in "othertable". I see serialization failures as a result of
*inserts* to atable in the context of:
'"SELECT 1 FROM ONLY othertable x WHERE "otherid" = $1 FOR SHARE OF
x" ' in 'INSERT INTO atable (otherid, co
