From: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
---|---|
To: | Jim Popovitch <jim(dot)popovitch(at)replatformtech(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: connection failures on forked processes |
Date: | 2022-06-13 03:43:25 |
Message-ID: | CAM9w-_nHfyR=QoGM1eKpQn91Jx07g4KjKJE+VZEthDzePsvZJQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Jim,
This is the pgAdmin mailing list. pgsql-hackers(at)postgresql(dot)org
<pgsql-support(at)postgresql(dot)org> is the email which might help.
On Fri, Jun 10, 2022 at 9:07 PM Jim Popovitch <
jim(dot)popovitch(at)replatformtech(dot)com> wrote:
> Hello!
>
> We are seeing connection failures when using "sslmode=require" on forked
> connections. Attached is example code that makes 2 passes. The first pass
> uses "sslmode=disable" and the second uses "sslmode=require". The first
> pass completes successfully, but the second pass fails. I'm looking for
> insight as to why this might be happening.
>
> Note: we are very aware of the dev notes about forking, however know that
> we are not sharing the forked connection, we simply open the connection in
> the parent thread and then pass that to the child thread to use.
>
> Thank you for any insight,
>
> -Jim P.
>
--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | *edbpostgres.com*
<http://edbpostgres.com>
"Don't Complain about Heat, Plant a TREE"
From | Date | Subject | |
---|---|---|---|
Next Message | Aditya Toshniwal | 2022-06-13 05:36:30 | [pgAdmin][RM7468] Query history empty |
Previous Message | Jim Popovitch | 2022-06-10 15:37:33 | connection failures on forked processes |