Re: Row Level Security − leakproof-ness and performance implications - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: Row Level Security − leakproof-ness and performance implications
Date
Msg-id 60db8234-b2c8-75b1-ea27-2495ea6cbef4@anastigmatix.net
Whole thread Raw
In response to Re: Re: Row Level Security − leakproof-ness and performance implications  (Joshua Brindle <joshua.brindle@crunchydata.com>)
List 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


pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Add exclusive backup deprecation notes to documentation
Next
From: Joe Conway
Date:
Subject: Re: Row Level Security − leakproof-ness and performance implications