Re: Nested transactions and tuple header info - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Nested transactions and tuple header info
Date
Msg-id 26349.1087147325@sss.pgh.pa.us
Whole thread Raw
In response to Re: Nested transactions and tuple header info  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Responses Re: Nested transactions and tuple header info
List pgsql-hackers
Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> Not sure how to fix this -- I'm not even sure what the exact problem is,
> because it's trying to insert the oid of a toast table in
> pg_class_oid_index during the first ALTER TABLE ... CREATE TOAST TABLE.
> Why would it see an old tuple with the same value, I don't know.

This is probably an UPDATE operation not an INSERT.  There are quite a
few paths through CREATE TABLE that involve repeated updates of the
new pg_class row.

I would think however that these changes would occur as successive
commands of a single transaction, not as subtransactions, unless you've
done something odd to CommandCounterIncrement.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Release 7.4.3 branded
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql-server: Clean up generation of