Re: BUG #15006: "make check" error if current user is "user"

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, eshkinkot(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15006: "make check" error if current user is "user"
Date: 2018-01-18 18:58:19
Message-ID: 20180118185819.pwvzqjaumvaeoaas@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:
> Michael Paquier <michael(dot)paquier(at)gmail(dot)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.

Have at it.

This all comes from
https://www.postgresql.org/message-id/20141010.172740.88258644.horiguchi.kyotaro@lab.ntt.co.jp
which ended up as commit 31eae6028eca4365e7165f5f33fee1ed0486aee0 (with
a couple of fixups afterwards).

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dave Cramer 2018-01-18 19:33:35 Re: BUG #15013: JNI-JDBC: org.postgresql.util.PSQLException: FEHLER: ungültiges Message-Format
Previous Message Joe Conway 2018-01-18 16:39:14 Re: BUG #15006: "make check" error if current user is "user"