| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Joshua Brindle <joshua(dot)brindle(at)crunchydata(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Row Level Security − leakproof-ness and performance implications |
| Date: | 2019-02-28 16:13:41 |
| Message-ID: | 60db8234-b2c8-75b1-ea27-2495ea6cbef4@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/28/19 11:03 AM, Joshua Brindle wrote:
> How is leakproof defined WRT Postgres? Generally speaking a 1 bit
From the CREATE FUNCTION reference page:
LEAKPROOF indicates that the function has no side effects. It reveals no
information about its arguments other than by its return value. For
example, a function which *throws an error message for some argument
values but not others*, or which includes the argument values in any
error message, is not leakproof.
(*emphasis* mine.)
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2019-02-28 16:14:50 | Re: Row Level Security − leakproof-ness and performance implications |
| Previous Message | Laurenz Albe | 2019-02-28 16:08:05 | Re: Add exclusive backup deprecation notes to documentation |