From: | Douglas McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Mark Woodward <pgsql(at)mohawksoft(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_service.conf |
Date: | 2006-02-19 14:58:01 |
Message-ID: | 87d5hjtmyu.fsf@suzuka.mcnaught.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> A server-side (i.e. centrally managed) name server seems like an
> improvement over the client-side solutions described, IMHO, but I'd
> leave it to others to describe how that might work. (e.g. DNS is a
> better solution than multiple distributed /etc/hosts files).
Funnily enough, you could *use* DNS for this--you could define a
custom RR type containing hostname, port, database etc and have
entries in DNS for each "service" (e.g. 'production-db.mycorp.com').
I think HESIOD used this mechanism.
Of course, you'd need an internal DNS server that you had full control
over...
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Woodward | 2006-02-19 15:00:01 | pg_service.conf |
Previous Message | Martijn van Oosterhout | 2006-02-19 14:53:45 | Re: pg_service.conf |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Woodward | 2006-02-19 15:00:01 | pg_service.conf |
Previous Message | Martijn van Oosterhout | 2006-02-19 14:53:45 | Re: pg_service.conf |