Re: No toast table for pg_shseclabel but for pg_seclabel

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>,Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, 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: 2015-03-22 09:27:14
Message-ID: 7F3B1933-6B79-4153-AA78-26136E44057A@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On March 22, 2015 3:15:07 AM GMT+01:00, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>On Thu, Mar 19, 2015 at 11:50:36AM -0400, Bruce Momjian wrote:
>> > Then there's the other discussion about using the security labels
>> > structure for more than just security labels, which could end up
>with a
>> > lot of other use-cases where the "label" is even larger.
>>
>> OK, the attached patch adds a TOAST table to the shared table
>> pg_shseclabel for use with long labels. The new query output shows
>the
>> shared and non-shared seclabel tables now both have TOAST tables:
>>
>> test=> SELECT oid::regclass, reltoastrelid FROM pg_class WHERE
>relname IN ('pg_seclabel', 'pg_shseclabel');
>> oid | reltoastrelid
>> ---------------+---------------
>> pg_seclabel | 3598
>> pg_shseclabel | 4060
>> (2 rows)
>>
>> Previously pg_shseclabel was zero.
>
>Patch applied.

Thanks.

--
Please excuse brevity and formatting - I am writing this on my mobile phone.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-03-22 09:28:04 Re: Lets delete src/test/performance
Previous Message Andres Freund 2015-03-22 09:26:49 Re: INT64_MIN and _MAX