From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: How to prohibit parallel scan through tableam? |
Date: | 2019-12-03 21:24:14 |
Message-ID: | 20191203212414.qp4s2wljeodaz3xu@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2019-11-27 16:10:20 +0300, Konstantin Knizhnik wrote:
> On 27.11.2019 15:12, Rafia Sabih wrote:
> > On Wed, 27 Nov 2019 at 12:33, Konstantin Knizhnik
> > <k(dot)knizhnik(at)postgrespro(dot)ru <mailto:k(dot)knizhnik(at)postgrespro(dot)ru>> wrote:
> >
> > Hi hackers,
> >
> > I wonder how it is possible to prohibit parallel scan for the
> > external
> > storage accessed through tableam?
> > For example if I want to implement specialized tableam for fast
> > access
> > to temp tables, how can I inform optimizer that
> > parallel scan is not possible (because table data is local to the
> > backend)?
> >
> > How about setting parallel_setup_cost to disable_cost in costsize.c for
> > your specific scan method.
>
> How can I do it if i just implementing my AM and not going to change any
> postgres code?
I think a set_rel_pathlist hook that prevents parallel paths from being
considered would be your best bet for now. But I encourage you to
suggest a patch to tableam to support it properly in future releases.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Karl O. Pinc | 2019-12-03 21:45:11 | Re: Patch to document base64 encoding |
Previous Message | Andres Freund | 2019-12-03 21:22:17 | Re: How to prohibit parallel scan through tableam? |