Re: pg_upgrade: convert on read is dead end - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: pg_upgrade: convert on read is dead end
Date
Msg-id 48F30DCE.9070305@enterprisedb.com
Whole thread Raw
In response to Re: pg_upgrade: convert on read is dead end  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Responses Re: pg_upgrade: convert on read is dead end
List pgsql-hackers
Zdenek Kotala wrote:
> Heikki Linnakangas napsal(a):
>> Besides, the "read all formats" approach wouldn't really avoid it 
>> either. If you passed a toasted datum to a function, when the function 
>> needs to detoast it, detoast_datum still wouldn't know whether the 
>> datum is in old or new format. You'd still need to detoast all values 
>> in the tuple somewhere before they could be passed around.
> 
> If you look into pg_upgrade prototype patch I added page version 
> information into HeapTupleData structure. It keeps information about 
> format. All chunked data are stored on a pages with same page versions. 
> I think these two things are enough to have all necessary information.

Functions are passed just a Datum, not HeapTupleData.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Markus Wanner
Date:
Subject: Re: The Axe list
Next
From: ITAGAKI Takahiro
Date:
Subject: Convert check constraints into One-Time_Filter on prepared statements