Re: bootstrap pg_shseclabel in relcache initialization

From: Adam Brightwell <adam(dot)brightwell(at)crunchydata(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bootstrap pg_shseclabel in relcache initialization
Date: 2015-11-10 18:10:32
Message-ID: CAE_9P=i0Z3zJ_5Sgt5pDe1jE+HfdpxUhwgUw4FhuoLYPrW4bcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 10, 2015 at 9:18 AM, Adam Brightwell
<adam(dot)brightwell(at)crunchydata(dot)com> wrote:
>> I'm with Alvaro: the most interesting question here is why that mistake
>> did not blow up on you immediately. I thought we had enough safeguards
>> in place to catch this type of error.
>
> Ok, I'll explore that a bit further as I was able to build and use
> with my hook without any issue. :-/

Ok, I have verified that it does indeed eventually raise a warning
about this. It took a few for it to occur/appear in my logs. I was
expecting it to be more "immediate". At any rate, I don't believe
there are any issues with the safeguards in place.

-Adam

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-11-10 18:22:03 Re: Uh-oh: documentation PDF output no longer builds in HEAD
Previous Message Magnus Hagander 2015-11-10 18:01:44 Re: Uh-oh: documentation PDF output no longer builds in HEAD