Re: libpq async connection and multiple hosts

From: Jelte Fennema <postgres(at)jeltef(dot)nl>
To: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: libpq async connection and multiple hosts
Date: 2023-10-26 08:00:53
Message-ID: CAGECzQQ1RL0jUTQ_zHQ0+9E26zCMFwBo4V05kd+xqLCgFVcxjg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 26 Oct 2023 at 03:31, Daniele Varrazzo
<daniele(dot)varrazzo(at)gmail(dot)com> wrote:
> The goal here was only non-blocking name resolution. Ahaini understand we should do is to split on the hosts for sync connections too, shuffle if requested, and make separate connection attempts.

If you pack the resolved addresses in same connection string then it
should be fine. The different hostaddrs will be shuffled by libpq.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2023-10-26 08:04:25 Re: Reconcile stats in find_tabstat_entry() and get rid of PgStat_BackendFunctionEntry
Previous Message Michael Paquier 2023-10-26 07:39:26 Re: pg_upgrade and logical replication