Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, nicolas(at)marchildon(dot)net, Bugs for PostgreSQL <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd
Date: 2013-12-09 21:45:39
Message-ID: 20131209214539.GL6777@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian wrote:

> return STATUS_ERROR;
> }
>
> ! user_name = get_user_name(&errstr);
> ! if (!user_name)
> {
> ! ereport(LOG, (errmsg("%s\n", errstr)));
> ! pfree(errstr);
> return STATUS_ERROR;
> }

The message is already translated by get_user_name, so I think this
should use errmsg_internal() instead of errmsg(). Also, why do you add
a newline?

Not clear whether the new file should be in src/port or src/common.

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2013-12-10 00:46:30 Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd
Previous Message Tom Lane 2013-12-09 21:35:56 Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd