Re: Rethinking TupleTableSlot deforming - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Rethinking TupleTableSlot deforming
Date
Msg-id 11346.1469220780@sss.pgh.pa.us
Whole thread Raw
In response to Re: Rethinking TupleTableSlot deforming  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2016-07-22 15:00:32 -0400, Tom Lane wrote:
>> Well, it's a question of whether an extra projection at the scan level is
>> worth the savings in column access during the sort or group stage.

> Well, the projection is what I was thinking of.

One point here is that unless your test case is a blind "SELECT *",
there's almost certainly going to be a projection before a sort anyway,
because we always want to get rid of any unreferenced columns to minimize
the data volume going through the sort.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug with plpgsql handling of NULL argument of compound type
Next
From: David Fetter
Date:
Subject: Re: [PROPOSAL] Temporal query processing with range types