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

From Jeff
Subject Re: Reducing overhead for repeat de-TOASTing
Date
Msg-id A959131D-B4CF-4059-9BB3-7DDF3E596ADC@torgo.978.org
Whole thread Raw
In response to Reducing overhead for repeat de-TOASTing  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Reducing overhead for repeat de-TOASTing  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jun 16, 2008, at 3:35 PM, Tom Lane wrote:

>
> to a cache entry rather than a freshly palloc'd value.  The cache  
> lookup
> key is the toast table OID plus value OID.  Now pg_detoast_datum()  
> has no
...
> 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?

--
Jeff Trout <jeff@jefftrout.com>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/





pgsql-hackers by date:

Previous
From: Robert Treat
Date:
Subject: Re: Crash in pgCrypto?
Next
From: Andrew Dunstan
Date:
Subject: Re: Crash in pgCrypto?