Re: Psql meta-command conninfo+

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Cc: Maiquel Grassi <grassi(at)hotmail(dot)com(dot)br>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Hunaid Sohail <hunaidpgml(at)gmail(dot)com>
Subject: Re: Psql meta-command conninfo+
Date: 2025-06-12 14:25:22
Message-ID: f4ff9294-b491-4053-83f5-11c10ab8c999@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21.02.25 19:19, Alvaro Herrera wrote:
> I suggest the attached, which gets 99% there with 10% of the
> complexity, and has \conninfo (no plus sign) output this:
>
> Connection Information
> Parámetro │ Valor
> ───────────────────────┼────────────────────────
> Base de Datos │ alvherre
> Client User │ alvherre
> Host │ 192.168.178.37
> Port │ 55432
> Opciones │
> Protocol Version │ 3
> Password Used? │ false
> GSSAPI Authenticated? │ false
> Backend PID │ 1589499
> TLS Connection? │ true
> TLS Library │ OpenSSL
> TLS Protocol │ TLSv1.3
> TLS Key Bits │ 256
> TLS Cipher │ TLS_AES_256_GCM_SHA384
> TLS Compression │ false
> ALPN │ postgresql
> Superuser? │ on
> Hot standby? │ off
> (18 filas)

This new code uses the term "TLS" where the rest of PostgreSQL,
including the rest of psql, uses the term "SSL". Making this different
seems uselessly confusing. I suggest the attached patch to use "SSL"
here as well.

Attachment Content-Type Size
0001-psql-Change-new-conninfo-to-use-SSL-instead-of-TLS.patch text/plain 3.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrice Chapuis 2025-06-12 14:27:58 Re: failover logical replication slots
Previous Message Konstantin Knizhnik 2025-06-12 14:22:22 Re: Non-reproducible AIO failure