Re: Making joins involving ctid work for the benefit of UPSERT - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Making joins involving ctid work for the benefit of UPSERT
Date
Msg-id CAM3SWZQ+wWWGuCO7Tz9qwOkxxtpcqBAF648rBqfVx5MEJpKq6w@mail.gmail.com
Whole thread Raw
In response to Making joins involving ctid work for the benefit of UPSERT  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Thu, Jul 17, 2014 at 6:18 PM, Peter Geoghegan <pg@heroku.com> wrote:
> This appears to be a Simple Matter of Programming (at least
> for someone that happens to already have a good understanding of the
> optimizer), and is anticipated by this comment within tidpath.c:
>
>  * 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.

By the way, this comment is obsolete since best_inner_indexscan() was
removed in 2012 by the parameterized paths patch.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Kouhei Kaigai
Date:
Subject: Re: [v9.5] Custom Plan API
Next
From: Thor Lancelot Simon
Date:
Subject: Re: PostgreSQL for VAX on NetBSD/OpenBSD