On Thu, Aug 27, 2020 at 03:41:40PM -0400, Bruce Momjian wrote: > On Thu, Aug 27, 2020 at 04:09:25PM +0900, Kyotaro Horiguchi wrote: > > At Wed, 26 Aug 2020 18:36:50 -0400, Bruce Momjian <br...@momjian.us> wrote > > in > > bruce> On Wed, Aug 26, 2020 at 06:13:23PM +0900, Kyotaro Horiguchi wrote: > > > > At Tue, 25 Aug 2020 22:52:44 -0400, Bruce Momjian <br...@momjian.us> > > > > wrote in > > > > > > Because we think we need any named value for every alternatives > > > > > > including the default value? > > > > > > > > > > Well, not putting clientcert at all gives the default behavior, so why > > > > > have clientcert=no-verify? > > > > > > > > clientcert=verify-ca or verify-full don't allow absence of client > > > > certificate. We need an option to allow the absence. > > > > > > Isn't the option not specifying clientcert? Here are some valid > > > pg_hba.conf lines: > > > > Sorry for the ambiguity. Perhaps I understand that we talked at > > different objects. I was mentioning about the option value that is > > stored *internally*, concretely the values for the struct member > > port->hba->clientcert. You are talking about the descriptive option in > > pg_hba.conf.
Yes, I realize we need an internal vaue for this, but it doesn't need to be visible to the user. -- Bruce Momjian <br...@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
