| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Andres Freund <andres(at)2ndquadrant(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: No toast table for pg_shseclabel but for pg_seclabel |
| Date: | 2014-10-11 20:38:22 |
| Message-ID: | 20141011203822.GF21267@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 4, 2014 at 10:53:15AM -0400, Tom Lane wrote:
> Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> writes:
> > Here is no other reason than what Alvaro mentioned in the upthread.
> > We intended to store security label of SELinux (less than 100bytes at most),
> > so I didn't think it leads any problem actually.
>
> > On the other hands, pg_seclabel was merged in another development cycle.
> > We didn't have deep discussion about necessity of toast table of pg_seclabel.
> > I added its toast table mechanically.
>
> So maybe we should get rid of the toast table for pg_seclabel. One less
> catalog table for a feature that hardly anyone is using seems like a fine
> idea to me ...
Is this still an open item?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-10-11 20:40:29 | Re: Performance regression: 9.2+ vs. ScalarArrayOpExpr vs. ORDER BY |
| Previous Message | Bruce Momjian | 2014-10-11 19:20:42 | Re: uninitialized values in revised prepared xact code |