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

From Peter Eisentraut
Subject Re: Row Level Security − leakproof-ness and performance implications
Date
Msg-id a5f0f8ec-bcdb-154b-be27-4109ee18edfa@2ndquadrant.com
Whole thread Raw
In response to Re: Row Level Security − leakproof-ness and performance implications  (Joe Conway <mail@joeconway.com>)
Responses Re: Row Level Security − leakproof-ness and performance implications
List pgsql-hackers
On 2019-02-28 00:03, Joe Conway wrote:
> What if we provided an option to redact all client messages (leaving
> logged messages as-is). Separately we could provide a GUC to force all
> functions to be resolved as leakproof. Depending on your requirements,
> having both options turned on could be perfectly acceptable.

There are two commit fest entries for this thread, one in Pierre's name
and one in yours.  Is your entry for the error message redacting
functionality?  I think that approach has been found not to actually
satisfy the leakproofness criteria.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: jsonpath
Next
From: Nikolay Shaplov
Date:
Subject: Re: [PATCH][PROPOSAL] Add enum releation option type