Re: Restructuring Paths to allow per-Path targetlist info

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Subject: Re: Restructuring Paths to allow per-Path targetlist info
Date: 2016-02-19 19:58:12
Message-ID: 26174.1455911892@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2016-02-19 20:02:24 Re: [HACKERS] The number of bytes is stored in index_size of pgstatindex() ?
Previous Message Andres Freund 2016-02-19 19:33:27 Re: FDW: should GetFdwRoutine be called when drop table?