From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Gajus Kuizinas <gajus(at)gajus(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: IMMUTABLE and PARALLEL SAFE function markings |
Date: | 2018-11-27 00:14:35 |
Message-ID: | 20181127001435.GL3415@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Vik Fearing (vik(dot)fearing(at)2ndquadrant(dot)com) wrote:
> On 27/11/2018 01:10, Stephen Frost wrote:
> > * Vik Fearing (vik(dot)fearing(at)2ndquadrant(dot)com) wrote:
> >> On 27/11/2018 01:05, Stephen Frost wrote:
> >>> That said, I do *not* think we should make any assumptions here- users
> >>> incorrectly mark things all the time but we shouldn't encourage that and
> >>> we shouldn't assume that functions marked as immutable are parallel
> >>> safe.
> >>
> >> Does that mean we also shouldn't assume that functions marked as
> >> immutable are index safe?
> >
> > We've got an index safe flag?
>
> Yes. It's called provolatile='i'.
... and we complain if someone tries to use a provolatile <> 'i'
function directly in an index, so not sure what you're getting at here?
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2018-11-27 00:16:00 | Re: pg_config wrongly marked as not parallel safe? |
Previous Message | Joe Conway | 2018-11-27 00:14:24 | Re: pg_config wrongly marked as not parallel safe? |