Re: Obsolete comment in tidpath.c

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Obsolete comment in tidpath.c
Date: 2015-10-06 21:01:06
Message-ID: CA+TgmoYQN00XB9HJnGNPx7HtSi9f9anTakXxJxK9Wgq_5Y1F2Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 5, 2015 at 3:05 AM, Etsuro Fujita
<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> I think "best_inner_indexscan()" in the following comment in tidpath.c
> is obsolete.
>
> * There is currently no special support for joins involving CTID; in
> * particular nothing corresponding to best_inner_indexscan(). Since it's
> * not very useful to store TIDs of one table in another table, there
> * doesn't seem to be enough use-case to justify adding a lot of code
> * for that.
>
> How about s/best_inner_indexscan()/parameterized scans/?

I'm not sure that's altogether clear.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-10-06 21:19:04 Re: Foreign join pushdown vs EvalPlanQual
Previous Message Robert Haas 2015-10-06 20:58:08 Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.