Re: Reducing overhead for repeat de-TOASTing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Reducing overhead for repeat de-TOASTing
Date: 2008-06-18 13:45:35
Message-ID: 26164.1213796735@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> You've not covered the idea that we just alter the execution so we just
> detoast once.

That's because I already considered and rejected that idea. There's
no very good place to do it. See thread on postgis-devel:

http://postgis.refractions.net/pipermail/postgis-devel/2008-June/003091.html

Aside from the problems mentioned there, there's the issue that a lower
plan level doesn't have any way to know whether the value will be needed
at all. We could look for references to the Var but it's entirely
possible that the Var is being passed to some function that doesn't
require a fully detoasted result. It wouldn't do for this
"optimization" to disable the slice-fetch feature...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-06-18 13:53:29 Re: [HACKERS] Hint Bits and Write I/O
Previous Message Simon Riggs 2008-06-18 10:52:01 Re: Reducing overhead for repeat de-TOASTing