Re: Problematic enforcement of "ERROR: functions in index predicate must be marked IMMUTABLE"

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: AviW(at)gilat(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Problematic enforcement of "ERROR: functions in index predicate must be marked IMMUTABLE"
Date: 2023-07-11 07:30:29
Message-ID: 20230711.163029.2291239725090453767.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

At Mon, 10 Jul 2023 21:28:12 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in
> In the end, adding such restrictions would just give a false sense
> of security, because there would always be gaps in whatever we did.
> As you quote from the documentation, volatility markings are a promise
> by the user to the system, not vice versa. If you break your promise,
> you get to keep both pieces of whatever trouble ensues.

I agree to you, as I mentioned a-bit-too-late message..

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-general by date

  From Date Subject
Next Message KK CHN 2023-07-11 08:50:24 BI Reports and Postgres
Previous Message Gurjeet Singh 2023-07-11 07:27:49 Re: how to return data from insert into ... on conflict ... returning ... into