From: | miyake_kouta <miyake_kouta(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] pgbench: Bug fix for the -d option |
Date: | 2021-03-05 02:26:45 |
Message-ID: | 9f87778b248f9bed876ad3b8455acd03@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2021-03-04 21:11, Michael Paquier wrote:
> Like any other src/bin/ facilities, let's instead
> remove all the getenv() calls at the beginning of pgbench.c and let's
> libpq handle those environment variables if the parameters are NULL
> (aka in the case of no values given directly in the options). This
> requires to move the debug log after doConnect(), which is no big deal
> anyway as a failure results in an exit(1) immediately with a log
> telling where the connection failed.
Thank you for improving my patch.
I agree that we should remove getenv() from pgbench.c and let libpq
complement parameters with environment variables.
As you said, it's not a big problem that the debug log output comes
after doConnect(), I think.
Your patch is simpler and more ideal.
Regards.
--
Kota Miyake
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2021-03-05 02:50:11 | 011_crash_recovery.pl intermittently fails |
Previous Message | Andy Fan | 2021-03-05 02:22:45 | Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series) |