From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitry Ivanov <d.ivanov@postgrespro.ru>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Possible problem in Custom Scan API
Date: Tue, 11 Apr 2017 13:57:04 -0400
Message-ID: <20021.1491933424@sss.pgh.pa.us> (raw)
In-Reply-To: <e29ddd30-8ef9-4da5-a50b-2bb7b8c7198d@postgrespro.ru>
References: <e29ddd30-8ef9-4da5-a50b-2bb7b8c7198d@postgrespro.ru>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Dmitry Ivanov <d.ivanov@postgrespro.ru> writes:
> 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.
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.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, d.ivanov@postgrespro.ru
Subject: Re: Possible problem in Custom Scan API
In-Reply-To: <20021.1491933424@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox