Re: [PATCH] pgbench: Bug fix for the -d option

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: miyake_kouta <miyake_kouta(at)oss(dot)nttdata(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] pgbench: Bug fix for the -d option
Date: 2021-03-05 09:35:47
Message-ID: 5594e01b-8390-f8c6-0493-a6df94ac0e36@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2021/03/05 16:33, Michael Paquier wrote:
> On Fri, Mar 05, 2021 at 01:30:11PM +0900, Fujii Masao wrote:
>> if ((env = getenv("PGDATABASE")) != NULL && *env != '\0')
>> dbName = env;
>> - else if (login != NULL && *login != '\0')
>> - dbName = login;
>> + else if ((env = getenv("PGUSER")) != NULL && *env != '\0')
>> + dbName = env;
>> else
>> - dbName = "";
>> + dbName = get_user_name_or_exit(progname);
>>
>> If dbName is set by libpq, the above also is not necessary?
>
> If you remove this part, pgbench loses some log information if
> PQconnectdbParams() returns NULL, like on OOM if the database name is
> NULL. Perhaps that's not worth caring about here for a single log
> failure, but that's the reason is why I left this part around.

Understood. Thanks!

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message torikoshia 2021-03-05 09:47:52 Re: Printing backtrace of postgres processes
Previous Message Magnus Hagander 2021-03-05 09:22:35 Re: PROXY protocol support