From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: hubert depesz lubaczewski <depesz@depesz.com>
Cc: pgsql-bugs mailing list <pgsql-bugs@postgresql.org>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Subject: Re: gen_random_uuid() is immutable in Pg 13devel
Date: Tue, 18 Feb 2020 17:58:03 -0500
Message-ID: <5848.1582066683@sss.pgh.pa.us> (raw)
In-Reply-To: <20200218200122.GA7247@alvherre.pgsql>
References: <20200218200122.GA7247@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, pg@bowt.ie, depesz@depesz.com, peter.eisentraut@2ndquadrant.com
Subject: Re: gen_random_uuid() is immutable in Pg 13devel
In-Reply-To: <5848.1582066683@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox