From: | Dmitry Ivanov <d(dot)ivanov(at)postgrespro(dot)ru> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Possible problem in Custom Scan API |
Date: | 2017-04-11 16:36:11 |
Message-ID: | e29ddd30-8ef9-4da5-a50b-2bb7b8c7198d@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi hackers,
I'm struggling to understand one particular thing about Custom Scan API.
As you may know, there's a function called use_physical_tlist(), which aims
to eliminate meaningless projections during query execution. Any scan node
(e.g. CustomScan) aims to take advantage of physical targetlists... except
for the IndexOnlyScan (for obvious reasons):
createplan.c, create_scan_plan():
if (use_physical_tlist(root, best_path, flags))
{
if (best_path->pathtype == T_IndexOnlyScan)
{
/* For index-only scan, the preferred tlist is the index's */
tlist = copyObject(((IndexPath *) best_path)->indexinfo->indextlist);
...
}
...
}
In theory, CustomScans should be able to use any Plan nodes (i.e.
'custom_plans' list), but as far as I can understand, there's no way to
override behavior of use_physical_tlist(), which means that we might see
something like this:
ERROR: variable not found in subplan target list
if we use child IndexOnlyScan and the index does not include some of the
relation's columns.
Is there any existing workaround?
--
Dmitry Ivanov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-04-11 16:51:29 | Re: Reversed sync check in pg_receivewal |
Previous Message | Tom Lane | 2017-04-11 16:32:12 | Re: [sqlsmith] ERROR: badly formatted node string "RESTRICTINFO... |