| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How to prohibit parallel scan through tableam? |
| Date: | 2019-12-03 21:22:17 |
| Message-ID: | 20191203212217.lxqvnffiw5n5thzy@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2019-11-27 14:33:42 +0300, Konstantin Knizhnik wrote:
> 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)?
I don't think there currently is a good way to do so - but it shouldn't
be hard to add that capability.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-12-03 21:24:14 | Re: How to prohibit parallel scan through tableam? |
| Previous Message | Alvaro Herrera | 2019-12-03 21:17:39 | Re: log bind parameter values on error |