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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 01:35:09
Message-ID: 20180118013509.GC29962@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jan 17, 2018 at 07:21:03PM -0500, Tom Lane wrote:
> I wouldn't have a big problem with just dropping this whole test stanza.
> It's an out-and-out violation of our rule against not creating rolenames
> not starting with "regress_", and it's not testing anything that seems
> especially likely to break.

Perhaps a stupid question. What's the point behind the logic to forbid a
double-quoted "public" but to authorize a double-quoted "user"? The
whole thing looks inconsistent to me.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-01-18 02:15:06 Re: BUG #15006: "make check" error if current user is "user"
Previous Message Tom Lane 2018-01-18 00:21:03 Re: BUG #15006: "make check" error if current user is "user"