Excerpts from Robert Young's message of vie oct 28 11:47:14 -0300 2011: > > 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.
I'm surprised that your conclusion was that the path of least resistance was submitting a patch to Postgres. Surely patching the apps would have been a lot easier. -- Á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
