Re: Obsolete comment in tidpath.c

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Obsolete comment in tidpath.c
Date: 2015-10-06 22:01:43
Message-ID: 7993.1444168903@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 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.

Probably consider_index_join_clauses() is the closest current equivalent.
However, it may not be such a great idea to have this comment referencing
a static function in another file, as it wouldn't occur to people to look
here when rewriting indxpath.c. (Ahem.)

Perhaps "in particular, no ability to produce parameterized paths here".

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2015-10-06 22:05:42 Re: pg_ctl/pg_rewind tests vs. slow AIX buildfarm members
Previous Message Andrew Dunstan 2015-10-06 21:59:23 Re: check fails on Fedora 23