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

From Andres Freund
Subject No toast table for pg_shseclabel but for pg_seclabel
Date
Msg-id 20140704095017.GN25909@awork2.anarazel.de
Whole thread Raw
Responses Re: No toast table for pg_shseclabel but for pg_seclabel  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Hi,

postgres=# SELECT oid::regclass, reltoastrelid FROM pg_class WHERE relname IN ('pg_seclabel', 'pg_shseclabel');     oid
    | reltoastrelid
 
---------------+---------------pg_seclabel   |          3598pg_shseclabel |             0
(2 rows)

Isn't that a somewhat odd choice? Why do we assume that there cannot be
lengthy seclabels on shared objects? Granted, most shared objects aren't
candidates for large amounts of data, but both users and databases don't
seem to fall into that category.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Escaping from blocked send() reprised.
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Escaping from blocked send() reprised.