| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Rework the pg_statistic_ext catalog |
| Date: | 2019-06-16 13:54:40 |
| Message-ID: | 13719.1560693280@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
> Anyway, I'm wondering if we need the REVOKE/GRANT on pg_statistic_ext at
> all, and if we do if we should just remove the list of columns, and
> grant SELECT on all. All the sensitive columns were moved to another
> catalog, after all.
+1. Per-column permissions checks seem pointlessly inefficient here.
> That also reminds me the patch should have revoked access to the new
> _data catalog.
Uh ... yeah.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-16 14:03:10 | Re: pgsql: Rework the pg_statistic_ext catalog |
| Previous Message | Tomas Vondra | 2019-06-16 11:20:21 | Re: pgsql: Rework the pg_statistic_ext catalog |