| From: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: How to prohibit parallel scan through tableam? |
| Date: | 2019-11-27 13:10:20 |
| Message-ID: | fb63b86e-f862-b6f9-b321-360ad11172a6@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2019-11-27 13:54:55 | Re: proposal: new polymorphic types - commontype and commontypearray |
| Previous Message | Andrey Borodin | 2019-11-27 12:47:25 | Re: pglz performance |