From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: pgsql-hackers@postgresql.org
Subject: Re: pg_stat_ssl additions
Date: Wed, 28 Nov 2018 16:01:31 -0500
Message-ID: <14681.1543438891@sss.pgh.pa.us> (raw)
In-Reply-To: <20181128173454.GF24817@momjian.us>
References: <398754d8-6bb5-c5cf-e7b8-22e5f0983caf@2ndquadrant.com>
<20181120.173122.55744021.horiguchi.kyotaro@lab.ntt.co.jp>
<01e7dd28-6bcc-5c26-a77d-54340a51633f@2ndquadrant.com>
<d8e4e6d9-4007-e115-86aa-8d5c2679696d@2ndquadrant.com>
<20181128173454.GF24817@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> On Wed, Nov 28, 2018 at 06:31:59PM +0100, Peter Eisentraut wrote:
>> Any thoughts from others about whether to rename clientdn to client_dn
>> to allow better naming of the new fields?
> Makes sense. The SSL acronyms can get very complex.
+1. It seems unlikely to me that there are very many applications out
there that have references to this view, so we can probably get away
with rationalizing the field names.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, peter.eisentraut@2ndquadrant.com, horiguchi.kyotaro@lab.ntt.co.jp
Subject: Re: pg_stat_ssl additions
In-Reply-To: <14681.1543438891@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox