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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: "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 02:51:21
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

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

regards, tom lane

In response to


Browse pgsql-bugs by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-01-18 05:48:51 Re: Index-only scan returns incorrect results when using a composite GIST index with a gist_trgm_ops column.
Previous Message Michael Paquier 2018-01-18 02:27:06 Re: BUG #15006: "make check" error if current user is "user"