Re: [PATCH] libpq: try all addresses for a host before moving to next on target_session_attrs mismatch

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Evgeny Kuzin <evgeny(dot)kuzin(at)outlook(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] libpq: try all addresses for a host before moving to next on target_session_attrs mismatch
Date: 2026-03-11 10:01:15
Message-ID: 0F9E3150-AF67-4523-984B-2D854DC9141B@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 11 Mar 2026, at 03:18, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> The question is whether the overall benefits of your proposal (which certainly makes sense
> in a setup like you describe) would be worth a performance and resource usage regression like
> the one I described above. Or can you see a way to modify your approach so that that problem
> can be avoided?

Version proposed by Andrew Jackson [0] adds a connection option check_all_addrs. Off by default.
This resolves potential problems of existing users.

Best regards, Andrey Borodin.

[0] https://commitfest.postgresql.org/patch/5396/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2026-03-11 10:04:55 Re: [Proposal] Adding Log File Capability to pg_createsubscriber
Previous Message Shin Berg 2026-03-11 09:54:01 Re: Inconsistency in owner assignment between INDEX and STATISTICS