Re: Restructuring Paths to allow per-Path targetlist info - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Restructuring Paths to allow per-Path targetlist info
Date
Msg-id 26174.1455911892@sss.pgh.pa.us
Whole thread Raw
In response to Re: Restructuring Paths to allow per-Path targetlist info  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> So, the attached patch just bites the bullet and adds explicit output
>> tlist information to struct Path.

> Hmm, I wonder if this can be used to attack the problem here in a more
> sensible manner:
> https://github.com/2ndQuadrant/postgres/commit/e7c5df6b614b542d55588a483dd2ddba3892a0f6

As far as I gather from that commit message, it wouldn't help much, because
everything discussed there happens before any Paths have been built.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: FDW: should GetFdwRoutine be called when drop table?
Next
From: Peter Geoghegan
Date:
Subject: Re: [DOCS] The number of bytes is stored in index_size of pgstatindex() ?