Re: can we mark upper/lower/textlike functions leakproof?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: can we mark upper/lower/textlike functions leakproof?
Date: 2024-08-01 14:26:05
Message-ID: 3737863.1722522365@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> On 8/1/24 07:17, Laurenz Albe wrote:
>> But what do you tell the users who would not accept that risk?

> Document that the option should not be used if that is the case

Are you proposing that we invent two levels of leakproofness
with different guarantees? That seems like a mess, not least
because there are going to be varying opinions about where we
should set the bar for the lower level.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-08-01 14:34:20 Re: Query results vary depending on the plan cache mode used
Previous Message Joe Conway 2024-08-01 14:05:44 Re: can we mark upper/lower/textlike functions leakproof?