I just migrate some services from one machine to another but database stay there. So, I think the most simple solution is to change “localhost” point to the new one, so that I need no modification of client applications. But found PG gave warnings.
On Fri, Oct 28, 2011 at 13:39, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > > Excerpts from Robert Young's message of vie oct 28 04:11:57 -0300 2011: >> I am just wondering, why "localhost" entry in /etc/hosts is editable >> and why 127.0.0.1 not fixed with loopback interface? >> should you agree with that we should submit a patch to kernel to >> resolve "localhost" to 127.0.0.1 statically need no entry in >> /etc/hosts and loopback interface bind to 127.0.0.1 not changeable? >> If your answer is NO. > > Maybe you can define localhost as an IPv6 address. > > >> Why you give me this option to configure /etc/hosts or loopback >> interface as well as deprive my option which hostname or IP for >> statistics_collector to listen on? >> Why operating system designed flexible and database system wrote in >> hard-coding? > > Are you solving a real problem here? > > -- > Álvaro Herrera <alvhe...@commandprompt.com> > The PostgreSQL Company - Command Prompt, Inc. > PostgreSQL Replication, Consulting, Custom Development, 24x7 support > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
