Re: BUG #15006: "make check" error if current user is "user" - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15006: "make check" error if current user is "user"
Date
Msg-id 13226.1516243881@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15006: "make check" error if current user is "user"  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: BUG #15006: "make check" error if current user is "user"
Re: BUG #15006: "make check" error if current user is "user"
List pgsql-bugs
Michael Paquier <michael.paquier@gmail.com> writes:
> On Wed, Jan 17, 2018 at 09:15:06PM -0500, Tom Lane wrote:
>> Probably the OP would not be very happy if the outcome of this discussion
>> is that "initdb -U user" fails, but I am not seeing a principled reason
>> why that should be allowed.

> Me neither.

Alternatively, we could consider removing all these artificial
restrictions on what a username can be, and just expecting the DBA
to know what he's doing.  But what we've got right now is weirdly
inconsistent.

            regards, tom lane


pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #15006: "make check" error if current user is "user"
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Index-only scan returns incorrect results when using acomposite GIST index with a gist_trgm_ops column.