Re: No toast table for pg_shseclabel but for pg_seclabel - Mailing list pgsql-hackers

From Tom Lane
Subject Re: No toast table for pg_shseclabel but for pg_seclabel
Date
Msg-id 20599.1404485595@sss.pgh.pa.us
Whole thread Raw
In response to Re: No toast table for pg_shseclabel but for pg_seclabel  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Responses Re: No toast table for pg_shseclabel but for pg_seclabel
List pgsql-hackers
Kohei KaiGai <kaigai@kaigai.gr.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 ...
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cluster name in ps output
Next
From: Abhijit Menon-Sen
Date:
Subject: Re: [REVIEW] Re: Compression of full-page-writes