Request a Demo
Home   >   mailing lists

Re: [PATCH] libpq: try all addresses for a host before moving to next on target_session_attrs mismatch - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: [PATCH] libpq: try all addresses for a host before moving to next on target_session_attrs mismatch
Date
Msg-id 0F9E3150-AF67-4523-984B-2D854DC9141B@yandex-team.ru
Whole thread Raw
In response to Re: [PATCH] libpq: try all addresses for a host before moving to next on target_session_attrs mismatch  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: [PATCH] libpq: try all addresses for a host before moving to next on target_session_attrs mismatch
List pgsql-hackers
Tree view 

> On 11 Mar 2026, at 03:18, Laurenz Albe <laurenz.albe@cybertec.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/

pgsql-hackers by date:

Previous
From: Shin Berg
Date:
Subject: Re: Inconsistency in owner assignment between INDEX and STATISTICS
Next
From: vignesh C
Date:
Subject: Re: [Proposal] Adding Log File Capability to pg_createsubscriber