Re: Possible problem in Custom Scan API

From: Dmitry Ivanov <d(dot)ivanov(at)postgrespro(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dmitry Ivanov <d(dot)ivanov(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Possible problem in Custom Scan API
Date: 2017-04-18 06:30:53
Message-ID: 1dc20861-189b-4349-bb2e-9bfb2c86bb9f@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> I'm unimpressed by this part --- we couldn't back-patch such a change, and
> I think it's unnecessary anyway in 9.6+ because the scan provider could
> generate a nondefault pathtarget if it wants this to happen.

You're right, of course. Thank you very much!

--
Dmitry Ivanov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kang Yuzhe 2017-04-18 06:31:20 Re: On How To Shorten the Steep Learning Curve Towards PG Hacking...
Previous Message Noah Misch 2017-04-18 06:07:44 Re: identity columns