Re: Multivariate MCV stats can leak data to unprivileged users - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: Multivariate MCV stats can leak data to unprivileged users
Date
Msg-id CAEZATCW3iAJnU8opUCXb2i_-8syU7on4cdXLWHBeWr04v67HoQ@mail.gmail.com
Whole thread Raw
In response to Re: Multivariate MCV stats can leak data to unprivileged users  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Multivariate MCV stats can leak data to unprivileged users  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Sat, 18 May 2019 at 16:13, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Dean Rasheed <dean.a.rasheed@gmail.com> writes:
> > On the other hand, pg_dump relies on pg_statistic_ext to work out
> > which extended statistics objects to dump. If we were to change that
> > to use pg_stats_ext, then a user dumping a table with RLS using the
> > --enable-row-security flag wouldn't get any extended statistics
> > objects, which would be a somewhat surprising result.
>
> It seems like what we need here is to have a separation between the
> *definition* of a stats object (which is what pg_dump needs access
> to) and the current actual *data* in it.  I'd have expected that
> keeping those in separate catalogs would be the thing to do, though
> perhaps it's too late for that.
>

Yeah, with the benefit of hindsight, that would have made sense, but
that seems like a pretty big change to be attempting at this stage.

Regards,
Dean



pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Fix some unique identifiers/entities
Next
From: Andrew Dunstan
Date:
Subject: Re: How to install login_hook in Postgres 10.5