> On May 2, 2023, at 12:15, Tomas Pospisek wrote:
>
> Oh, I think your idea to use pgbouncer to take care of the SSL termination is
> elegant. I don't think me I'd characterize it as a hack if properly set up.
> Why do you consider it a hack?
It's really only a hack in the sense that
On 5/2/23 13:15, Tomas Pospisek wrote:
Oh, I think your idea to use pgbouncer to take care of the SSL
termination is elegant. I don't think me I'd characterize it as a hack
if properly set up. Why do you consider it a hack?
*t
Let me guess: postgres IS NOT listening on the other port,
On 02.05.23 12:13, Magnus Hagander wrote:
On Tue, May 2, 2023 at 11:43 AM sujay kadam wrote:
Hi PostgreSQL Team,
I want to enable SSL in PostgreSQL Database on a new port.
I don’t want the default port that is 5432 SSL enabled, but I want to configure
another port to enable SSL on it.
As
On Tue, May 2, 2023 at 11:43 AM sujay kadam wrote:
>
> Hi PostgreSQL Team,
>
>
> I want to enable SSL in PostgreSQL Database on a new port.
>
> I don’t want the default port that is 5432 SSL enabled, but I want to
> configure another port to enable SSL on it.
>
> As per my requirement, I cannot
Hi PostgreSQL Team,
I want to enable SSL in PostgreSQL Database on a new port.
I don’t want the default port that is 5432 SSL enabled, but I want to
configure another port to enable SSL on it.
As per my requirement, I cannot use the same port for normal connection and
SSL connection.
Hence,
