Re: Regarding SSL Enablement in PostgreSQL Database on different port

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: sujay kadam <sujaykadam02(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Regarding SSL Enablement in PostgreSQL Database on different port
Date: 2023-05-02 10:13:08
Message-ID: CABUevEwx7=cCE=SBW7kXamNbVN9Hk4+oMbS2cF0PSSM31HKdvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, May 2, 2023 at 11:43 AM sujay kadam <sujaykadam02(at)gmail(dot)com> 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 use the same port for normal connection and SSL connection.
>
> Hence, we require a new port to be SSL enabled.
>
>
> Please guide us with proper information and links to achieve the above task.

That is now how SSL in PostgreSQL works. It will always run on the
same port, and PostgreSQL will only listen on one port.

You can probably do some hacky solution to it by running something
like pgbouncer on a different port and enable SSL only in that one.
But it will be a hack. I would recommend instead reviewing your
requirements and see if you can make them work with how PostgreSQL is
designed.

--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Magnus Hagander 2023-05-02 10:15:53 Re: postgresql15-contrib installation on Amazon Linux 2 fails on Python shared lib dependency
Previous Message sujay kadam 2023-05-02 09:43:03 Regarding SSL Enablement in PostgreSQL Database on different port