Re: A bug with ALTER TABLE SET WITHOUT OIDS in CVS HEAD - Mailing list pgsql-hackers

From Tom Lane
Subject Re: A bug with ALTER TABLE SET WITHOUT OIDS in CVS HEAD
Date
Msg-id 27836.1227895233@sss.pgh.pa.us
Whole thread Raw
In response to Re: A bug with ALTER TABLE SET WITHOUT OIDS in CVS HEAD  (KaiGai Kohei <kaigai@ak.jp.nec.com>)
List pgsql-hackers
KaiGai Kohei <kaigai@ak.jp.nec.com> writes:
> In my understanding, the matter comes from the mixture of two kind of
> tuples. The one has object identifier, and the other don't have.
> It seems to me the current implementation assumes fetched tuples have
> proper rowtype which matches to the current table definition, however,
> the ALTER TABLE can break this assumption.

Right.  And the way to fix that is to fix ALTER TABLE to not break the
assumption.  Otherwise we'll be putting band-aids in different parts
of the system for years to come.  As I said when the point came up
originally, there is no reason to assume that this is a problem that
affects only one or two places.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Review: Hot standby
Next
From: "Guillaume Smet"
Date:
Subject: Re: Review: Hot standby