Re: Re: "pg_xxx" role name restriction not applied to bootstrap superuser?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, glyn(at)8kb(dot)co(dot)uk
Subject: Re: Re: "pg_xxx" role name restriction not applied to bootstrap superuser?
Date: 2016-05-08 16:07:37
Message-ID: 4780.1462723657@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> If we're going to enforce such a restriction, I think it would be
>> a good thing for it to be in place in beta1.

> Makes sense.
> Patch attached. I'll push this in a bit, barring objections.

Three minor wording quibbles:

* s/reserved/disallowed/ maybe? Not 100% sold on this.

* s/can not/cannot/

* use double quotes not single around pg_

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-05-08 16:28:13 Re: new tests post-feature freeze (was pgsql: Add TAP tests for pg_dump)
Previous Message Robert Haas 2016-05-08 15:59:35 Re: new tests post-feature freeze (was pgsql: Add TAP tests for pg_dump)