Re: HOT patch - version 15 - Mailing list pgsql-patches

From Tom Lane
Subject Re: HOT patch - version 15
Date
Msg-id 28216.1189521417@sss.pgh.pa.us
Whole thread Raw
In response to Re: HOT patch - version 15  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
Responses Re: HOT patch - version 15  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
Re: HOT patch - version 15  ("Heikki Linnakangas" <heikki@enterprisedb.com>)
List pgsql-patches
"Pavan Deolasee" <pavan.deolasee@gmail.com> writes:
> I would actually think twice before even doing this because this would
> lead to complete change in heap page structure and stop people from
> upgrading to 8.3 without a complete dump/restore. I don't remember 8.3
> introduces any other significant change which already enforces that.

Then you don't remember far enough --- either the HeapTupleHeader change
or the varvarlena change would be enough to prevent that.  For that
matter, the pd_flags header field that the patch is already relying on
is new for 8.3.

Adding an xmin field might or might not be a good solution, but to
complain about it on compatibility grounds is silly.

            regards, tom lane

pgsql-patches by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Final Thoughts for 8.3 on LWLocking and Scalability
Next
From: "Pavan Deolasee"
Date:
Subject: Re: HOT patch - version 15