pgsql: Make pg_shseclabel available in early backend startup

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Make pg_shseclabel available in early backend startup
Date: 2016-01-05 17:51:42
Message-ID: E1aGVlm-0002FY-S5@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Make pg_shseclabel available in early backend startup

While the in-core authentication mechanism doesn't need to access
pg_shseclabel at all, it's reasonable to think that an authentication
hook will want to look at the label for the role logging in, or for rows
in other catalogs used during the authentication phase of startup.

Catalog version bumped, because this changes the "is nailed" status for
pg_shseclabel.

Author: Adam Brightwell

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/efa318bcfac132c48dff8196f726e56a6843f06b

Modified Files
--------------
src/backend/utils/cache/relcache.c | 26 +++++++++++++++++---------
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_shseclabel.h | 7 +++++--
3 files changed, 23 insertions(+), 12 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-01-05 18:02:50 pgsql: Make the to_reg*() functions accept text not cstring.
Previous Message Tom Lane 2016-01-05 17:35:28 pgsql: Add to_regnamespace() and to_regrole() to the documentation.