| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, gajus(at)gajus(dot)com, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: IMMUTABLE and PARALLEL SAFE function markings |
| Date: | 2018-11-27 04:38:14 |
| Message-ID: | 6394.1543293494@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Nov 26, 2018 at 11:21 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Alternatively, could we postpone the parallelism checks till after
>> function inlining? Do we even make any before that?
> ... I believe the parallel-safety checks are done very early, and if
> you decide that it's not safe to proceed with parallelism, you can't
> really change your mind later.
What do you consider "very early"? I do not offhand see a good reason
why we would need to know that before entering query_planner. Before
that, by definition, we have not made any paths.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2018-11-27 04:56:09 | Re: pg11.1 jit segv |
| Previous Message | Robert Haas | 2018-11-27 04:31:52 | Re: IMMUTABLE and PARALLEL SAFE function markings |