Re: [HACKERS] Possible problem in Custom Scan API

Поиск
Список
Период
Сортировка
От Dmitry Ivanov
Тема Re: [HACKERS] Possible problem in Custom Scan API
Дата
Msg-id 1ef85b46-1385-4810-bb80-97cd977da1d5@postgrespro.ru
обсуждение исходный текст
Ответ на Re: [HACKERS] Possible problem in Custom Scan API  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [HACKERS] Possible problem in Custom Scan API
Список pgsql-hackers
Tom Lane wrote:
> Uh, why would you see that?  The planner would never generate an
> IndexOnlyScan in the first place if the query required any columns
> not available from the index.

True, but as you can see, create_append_plan() produces its own targetlist:

static Plan *
create_append_plan(PlannerInfo *root, AppendPath *best_path)
{Append       *plan;List       *tlist = build_path_tlist(root, &best_path->path);...

If we replace Append with some custom node, the plan will instantly become
invalid (it won't be be able to build a projection from 'custom_scan_tlist'
to 'targetlist'). However, this doesn't mean that it's unable to produce
the same result.


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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [HACKERS] bumping HASH_VERSION to 3
Следующее
От: Tom Lane
Дата:
Сообщение: [HACKERS] Why does logical replication launcher set application_name?