| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, 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 22:58:03 |
| Message-ID: | 5848.1582066683@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2020-Feb-18, Peter Geoghegan wrote:
>> 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.
Yeah. That default was chosen just to reduce the size of pg_proc.dat
(since a large majority of C functions are indeed immutable). But
it might be too error-prone this way. I remember worrying about that
when we put it in.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michail Nikolaev | 2020-02-18 23:01:38 | Re: BUG #16108: Colorization to the output of command-line has unproperly behaviors at Windows platform |
| Previous Message | Michail Nikolaev | 2020-02-18 22:39:39 | Re: BUG #16108: Colorization to the output of command-line has unproperly behaviors at Windows platform |