Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dUbOn-00082x-W3 for pgsql-bugs@arkaria.postgresql.org; Mon, 10 Jul 2017 16:19:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dUbOn-0007Mn-CJ for pgsql-bugs@arkaria.postgresql.org; Mon, 10 Jul 2017 16:19:01 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dUbOm-0007LS-K2 for pgsql-bugs@postgresql.org; Mon, 10 Jul 2017 16:19:00 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dUbOj-0001GW-KV for pgsql-bugs@postgresql.org; Mon, 10 Jul 2017 16:18:59 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v6AGIrma001839; Mon, 10 Jul 2017 12:18:54 -0400 From: Tom Lane To: fcs1@poczta.onet.pl cc: pgsql-bugs@postgresql.org Subject: Re: BUG #14738: ALTER SERVER for foregin servers not working In-reply-to: <20170710113917.7727.10247@wrigleys.postgresql.org> References: <20170710113917.7727.10247@wrigleys.postgresql.org> Comments: In-reply-to fcs1@poczta.onet.pl message dated "Mon, 10 Jul 2017 11:39:17 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1837.1499703533.1@sss.pgh.pa.us> Date: Mon, 10 Jul 2017 12:18:53 -0400 Message-ID: <1838.1499703533@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org fcs1@poczta.onet.pl writes: > PostgreSQL version: 9.4.1 > Command like this doesn't take effect: > ALTER SERVER srw_egib_1 > OPTIONS ( > SET host 'localhost', > SET port '5432', > SET dbname 'gml2m1'); > It changes definition of this server but tables connected to it are still > connected to previous definition of this server, for example: It would help if you provided a concrete example of misbehavior rather than abstract claims. However, I *think* this is something we fixed in 9.4.11. Please update and try again. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs