Re: Scans are offloaded to SeqScan instead of CustomScan when there are multiple relations in the same query

From: Amin <amin(dot)fallahi(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Scans are offloaded to SeqScan instead of CustomScan when there are multiple relations in the same query
Date: 2023-04-18 01:03:08
Message-ID: CAF-KA88U1G3rLCSkvQ=yg9Gfa_9Dq91H2tBKw=MDH5gYEFd0bQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Tom,

I made sure EXPLAIN returns CustomScan for all scans in the query. But
still, ExecCustomScan is only called once while the rest of the functions
are called for each scan separately. Is this expected behavior? How to work
around this?

Thank you!

On Mon, Apr 17, 2023 at 3:45 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Amin <amin(dot)fallahi(at)gmail(dot)com> writes:
> > To simplify: Can CustomScan scan multiple relations in the same query or
> it
> > will always be assigned to one or zero relations?
>
> There's barely any code in the core planner that is specific to custom
> scans. Almost certainly this misbehavior is the fault of your
> custom-path-creation code. Maybe you're labeling the paths with the
> wrong parent relation, or forgetting to submit them to add_path,
> or assigning them costs that are high enough to get them rejected?
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-04-18 01:35:00 Re: Fix typos and inconsistencies for v16
Previous Message Michael Paquier 2023-04-17 23:52:11 Re: check_strxfrm_bug()