| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | hubert depesz lubaczewski <depesz(at)depesz(dot)com>, pgsql-bugs mailing list <pgsql-bugs(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Subject: | Re: gen_random_uuid() is immutable in Pg 13devel |
| Date: | 2020-02-18 20:01:22 |
| Message-ID: | 20200218200122.GA7247@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2020-Feb-18, Peter Geoghegan wrote:
> On Tue, Feb 18, 2020 at 11:01 AM Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> > > It looks that commit 5925e5549890416bcf588334d9d0bc99f8ad6c7f forgot to
> > > mark the function as volatile. Not sure if it was intentional.
> >
> > It seems an oversight to me.
>
> Maybe this happened because the default volatility for pg_proc.dat
> entries is not 'volatile' -- it's 'immutable'.
That makes me wonder what should be the default --- and should there
even *be* a default in the first place? Maybe it's better to make
everyone *think* about it every time rather than hoping we'll all
remember, and frequently having it got wrong.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2020-02-18 20:34:01 | Re: gen_random_uuid() is immutable in Pg 13devel |
| Previous Message | Peter Geoghegan | 2020-02-18 19:36:00 | Re: gen_random_uuid() is immutable in Pg 13devel |