Re: Reducing overhead for repeat de-TOASTing - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Reducing overhead for repeat de-TOASTing
Date
Msg-id 19905.1213710555@sss.pgh.pa.us
Whole thread Raw
In response to Re: Reducing overhead for repeat de-TOASTing  (Jeff <threshar@torgo.978.org>)
List pgsql-hackers
Jeff <threshar@threshar.is-a-geek.com> writes:
> On Jun 16, 2008, at 3:35 PM, Tom Lane wrote:
>> the result of decompressing an inline-compressed datum, because those
>> have no unique ID that could be used for a lookup key.  This puts a
>> bit of a

> Wouldn't the tid fit this? or table oid + tid?

No.  The killer reason why not is that at the time we need to decompress
a datum, we don't know what row it came from.  There are some other
problems too...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: plan cache vs regclass constants
Next
From: David Fetter
Date:
Subject: sh -> pl