| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: assessing parallel-safety |
| Date: | 2015-02-12 11:40:18 |
| Message-ID: | CAA4eK1JQOfG+jfxfh6nAGbj9QoKro3_x6n2FZZ3=vD8QVdW6+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 12, 2015 at 1:51 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>
> I think we may want a dedicated parallel-safe property for functions
> rather than piggybacking on provolatile, but that will probably also
> be changeable via ALTER FUNCTION, and stored rules won't get
> miraculously updated. So this definitely can't be something we figure
> out at parse-time ... it's got to be determined later. But at the
> moment I see no way to do that without an extra pass over the whole
> rewritten query tree. :-(
>
If we have to go this way, then isn't it better to evaluate the same
when we are trying to create parallel path (something like in the
parallel_seq scan patch - create_parallelscan_paths())?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Urbański | 2015-02-12 11:43:08 | Re: libpq's multi-threaded SSL callback handling is busted |
| Previous Message | Kyotaro HORIGUCHI | 2015-02-12 11:28:10 | Re: How about to have relnamespace and relrole? |