Hi,
I was attempting to set up a high availability system using DNS and
target_session_attrs. I was using a DNS setup similar to below and was
trying to use the connection strings `psql postgresql://
u...@pg.database.com/db_name?target_session=read-write` to have clients
dynamically connect to the
The previous patch had a mistake in a reference in the documentation. This
should fix it.
On Mon, Feb 24, 2025 at 10:07 AM Andrew Jackson
wrote:
> Looks like this needed another rebase to account for the oauth commit.
> Rebase attached.
>
> On Mon, Feb 24, 2025 at 9:38 AM An
lieve some drivers choose to
traverse all addresses because they have users target the same use case
outlined above.
Thanks again,
Andrew Jackson
On Sun, Feb 16, 2025 at 6:03 AM Andrey Borodin wrote:
> Hi Andrew!
>
> cc Jelte, I suspect he might be interested.
>
> > On 20 Nov
Looks like this needed another rebase to account for the oauth commit.
Rebase attached.
On Mon, Feb 24, 2025 at 9:38 AM Andrew Jackson
wrote:
> Hi,
>
> Thank you for the review!
>
> Review Response
>
> - Made a first pass at a real commit message
> - Fixed the conditio
Currently the LDAP usage in fe-connect.c does not explicitly set the
protocol version to v3. This causes issues with many LDAP servers as they
will often require clients to use the v3 protocol and disallow any use of
the v2 protocol. Further the other usage of LDAP in postgres (in
`backend/libpq/au
Apologies, forgot to attach the patch in the prior email.
On Sat, Mar 22, 2025 at 4:10 PM Andrew Jackson
wrote:
> Currently the LDAP usage in fe-connect.c does not explicitly set the
> protocol version to v3. This causes issues with many LDAP servers as they
> will often require clien
strict in that it creates a dummy database
that is not started and passes all queries though that and tests that the
connection service file correctly overrides the environment variables set
by the dummy databases' query functions
Thanks,
Andrew Jackson
On Mon, Mar 31, 2025, 4:01 PM Ryo Kanba
17 00:00:00 2001
From: Peter Eisentraut
Date: Thu, 3 Apr 2025 15:06:13 +0200
Subject: [PATCH] libpq: Set LDAP protocol version 3
Some LDAP servers reject the default version 2 protocol. So set
version 3 before starting the connection. This matches how the
backend LDAP code
ection
Parameters" described in [3]
[0] https://github.com/lldap/lldap
[1] https://github.com/osixia/docker-openldap
[2] https://linux.die.net/man/3/ldap
[3] https://www.postgresql.org/docs/current/libpq-ldap.html
On Sat, Mar 22, 2025 at 6:10 PM Tom Lane wrote:
> Andrew Jackson
Hi,
Added some tests for the LDAP connection parameters lookup functionality
with the attached patch. It is based off of the tests that were added
recently that cover the connection service file libpq functionality as well
as the existing ldap test framework.
Thanks,
Andrew Jackson
On Wed, Mar
10 matches
Mail list logo
