From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: -d option for pg_isready is broken |
Date: | 2013-12-11 14:35:42 |
Message-ID: | 20131211143542.GA25227@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2013-12-11 08:56:43 -0500, Robert Haas wrote:
> > $ psql -d "hostaddr=127.0.0.1"
> > =# \conninfo
> > You are connected to database "postgres" as user "postgres" via socket
> > in "/tmp" at port "5432".
>
> Yeah, that's true. But the whole point of having both host and
> hostaddr seems to be that you can lie about where you're connecting.
> If you set host=some.pretty.domain.name hostaddr=1.2.3.4, the point is
> to say that you're connecting to the first while, under the covers,
> actually connecting to the second. Now, I am unclear what value this
> has, but someone at some point evidently thought it was a good idea,
> so we need to be careful about changing it.
One use case is accessing a particular host when using DNS round robin
to standbys in combination with SSL.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-12-11 14:43:38 | Re: autovacuum_work_mem |
Previous Message | Merlin Moncure | 2013-12-11 14:33:20 | Re: In-Memory Columnar Store |