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

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: eshkinkot(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org>
Subject: Re: BUG #15006: "make check" error if current user is "user"
Date: 2018-01-17 21:58:51
Message-ID: d67a0d73-fbc4-f0b3-a5fd-eb1fcb42b555@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On 01/11/2018 01:53 PM, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15006
> Logged by: Sergey Burladyan
> Email address: eshkinkot(at)gmail(dot)com
> PostgreSQL version: 10.1
> Operating system: Debian GNU/Linux 9 (stretch) in docker
> Description:
>
> I run tests in docker with current system user "user" and "make check" stop
> with error:
> ...
> updatable_views ... ok
> rolenames ... FAILED
> roleattributes ... ok
> ...
>

Hmmm ... I'm having this issue too (my distribution uses "user"
internally for the default user). Over time I managed to convince myself
it's not really a PostgreSQL bug, but rather a strange choice of OS user
name. And I've been simply ignoring this particular regression failure
on my laptop.

But maybe we could/should fix it anyway? Most regression tests switched
to roles prefixed with regress_* so why not to do the same here?

Of course, a particularly strange distribution could still pick a
conflicting OS name, but that seems rather unlikely, I guess.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2018-01-17 22:11:12 Re: BUG #15006: "make check" error if current user is "user"
Previous Message Tomas Vondra 2018-01-17 21:44:16 Re: BUG #15001: planner cann't distinguish composite index?