Re: new feature: LDAP database name resolution - Mailing list pgsql-hackers

From Albe Laurenz
Subject Re: new feature: LDAP database name resolution
Date
Msg-id 52EF20B2E3209443BC37736D00C3C13806FC091B@EXADV1.host.magwien.gv.at
Whole thread Raw
In response to new feature: LDAP database name resolution  ("Albe Laurenz" <all@adv.magwien.gv.at>)
Responses Re: new feature: LDAP database name resolution  (Martijn van Oosterhout <kleptog@svana.org>)
Re: new feature: LDAP database name resolution  (Russell Smith <mr-russ@pws.com.au>)
List pgsql-hackers
Thanks to everybody who answered.

Maybe it is really the best thing to use a tool like postgresql-relay or
pgpool - I will investigate these.
I'm not eager to reinvent the wheel.

We have considered relocating DNS entries, but the problem is that a
changed
DNS entry takes long to propagate; in particular Windows has a caching
problem there.

Thank you also for drawing my attention to pg_service.conf - I have not
been aware of it.
There are two 'shortcomings':
- It still means that you have to change the config file on every
client.
- This feature cannot be used with psql or ecpg, right?

Do you think that it is worth the effort for me to look into extending
the
pg_service.conf/PGSYSCONFDIR approach to LDAP (and changing psql to use
it)?

Yours,
Laurenz Albe


pgsql-hackers by date:

Previous
From: "R, Rajesh (STSD)"
Date:
Subject: [PATCH] ipv6 support for getaddrinfo.c
Next
From: Martijn van Oosterhout
Date:
Subject: Re: new feature: LDAP database name resolution