Make pg_shseclabel available in early backend startup
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 5 Jan 2016 17:50:53 +0000 (14:50 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 5 Jan 2016 17:50:53 +0000 (14:50 -0300)
commitefa318bcfac132c48dff8196f726e56a6843f06b
treeb37e27fafd2987b22329853d50ced5dcef25440e
parent83be1844acdcb0cbff31369a65ec61d588fbe9f3
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
src/backend/utils/cache/relcache.c
src/include/catalog/catversion.h
src/include/catalog/pg_shseclabel.h