| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| 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 19:44:36 |
| Message-ID: | d7b042e3470d69966c7a4745c2bb35272f15591d.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2026-03-11 at 15:01 +0500, Andrey Borodin wrote:
> > 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.
Ah, ok, I didn't read the patch. If resolving all addresses is disabled by default and
has to be enabled explicitly, I have no objection.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-03-11 19:50:23 | Re: support fast default for domain with constraints |
| Previous Message | Nazir Bilal Yavuz | 2026-03-11 19:22:18 | Re: Speed up COPY FROM text/CSV parsing using SIMD |