Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gR4X3-0006bS-IR for pgsql-hackers@arkaria.postgresql.org; Mon, 26 Nov 2018 00:13:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gR4X0-0003HX-BP for pgsql-hackers@arkaria.postgresql.org; Mon, 26 Nov 2018 00:13:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gR4X0-0003HQ-47 for pgsql-hackers@lists.postgresql.org; Mon, 26 Nov 2018 00:13:42 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gR4Wu-0007U9-1S for pgsql-hackers@postgresql.org; Mon, 26 Nov 2018 00:13:41 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A3E6021175; Sun, 25 Nov 2018 19:13:34 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 25 Nov 2018 19:13:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=il0kRgwMYN7Xe8D53GNiK0bqh6A /dFJ6VYbnAIryeeg=; b=GlPBl6/KOn0snlZWbXjN+TFx9lW/AgkEKhegLuPXXom 4apCQOASAZUWvEO9PR+RY1Qv38O4yC+d1hHcRHXK+kSfZz+JtQcmslylYZ3OOsLK mJFniKaQ4Ufl87BRqDk93kBdOcRPT30Mf1Jfn91yNyuwOhv5NbykWNltwTS0nSb5 TjVoW/afE3dWSptGf+903P/JfsNj8TkNG2c2FpOUzA/c93bF4RqTLOk7XgaW//3v dAuaxZ62vYyfEHHuMJrrNdJ9BjC6tK8hseOjISjRccXewDemHRxkYBXv6jkmhpRs atD35DALrnXBMz1ywW98HvSX2h6ittbrKCzZALqTS0A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=il0kRg wMYN7Xe8D53GNiK0bqh6A/dFJ6VYbnAIryeeg=; b=F2R9+UivejOL2NDuiGMrK/ 1MeQIMlTgm0AXlP6otKSkxkv31urZfGbC2I0cGNLSnbuOrWk7wNt8FwUQXkp0wog N22cdgh8aJrRu/gl2vKLN6K+KH78dH56feTyRd9OrqppWjOmAQc+c8H30DwdCrcw VEqqbe4uD+LmyILluiQO1wmq4V5kKqkBiIxGhN0g3H5P+awzGN3l2QMYJ0E9v4Ri /GoqsVJdgklMRtTR6UjgQVN63AZ8G5l6fb/oQ+3EM7oUkZJvksAjTbw5JjwZswC8 jDIFD1s3eitnelc/V4raA/R8kz0cLPCAxokcyf+19IC+y6583VMISb9F4N9O+UJA == X-ME-Sender: X-ME-Proxy: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id 36048E4678; Sun, 25 Nov 2018 19:13:31 -0500 (EST) Date: Mon, 26 Nov 2018 09:13:29 +0900 From: Michael Paquier To: Andres Freund Cc: Sergei Kornilov , PostgreSQL mailing lists Subject: Re: allow online change primary_conninfo Message-ID: <20181126001329.GC1776@paquier.xyz> References: <19513901543181143@sas1-19a94364928d.qloud-c.yandex.net> <20181125214313.lydvmrraqjfrb3s2@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Fig2xvG2VGoz8o/s" Content-Disposition: inline In-Reply-To: <20181125214313.lydvmrraqjfrb3s2@alap3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Fig2xvG2VGoz8o/s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 25, 2018 at 01:43:13PM -0800, Andres Freund wrote: > On 2018-11-26 00:25:43 +0300, Sergei Kornilov wrote: >> I think we have no futher reason to have a copy of conninfo and slot >> name in WalRcvData, so i propose remove these fields from >> pg_stat_get_wal_receiver() (and pg_stat_wal_receiver view). This data >> can be accesible now via regular GUC commands. >=20 > Is that wise? It seems possible that wal receivers run for a while with > the old connection information, and without this information that seems > hard to debug. No, that's unwise. One of the reasons why conninfo is around is that we know to which server a receiver is connected when specifying multiple host and/or port targets in the configuration. Please see 9a895462 for the details. Removing the slot does not look like an improvement to me either, following Andres' argument. -- Michael --Fig2xvG2VGoz8o/s Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlv7OqkACgkQnvQgOdby QH3KrQ/8DZ0HXt6sMLWLLyfQyFaUNB0st8JU4OHJN9i6WNqXdUvg1TkHcAptSGPQ hX1gpkUEp7DHE76ZdX5/1p9v54zcMlLLsxyyNUSRVKwFRdv2YcXTTpiL8GlJhYPK BedAxcTX+0VpBKMMwsPLiihK6Er5d7j6Y18ATQAp2+V95B0Yz2OojqyKWA/MEvcp nTPueSPq28ETaD5+u511++oB+eKqyo+VxvaN0sXBqbIBDaQuhFprSygbDbvAN5kd nmQLkzMn7b2KVRJNxlKHAalfTryBhP07xSMG4+xuWskN2aM5K1/I7P/3XmEP2iuw Ymo6L2IJJOhDxE0rM3ad9dTyJ1Ynbbm7ww51ikriiD4rVcqdxDAx+ge/gSTi846d moQxW1FvtPi/myLnq9zqtm8JH0+MCCL79Dw3q8nr0Do+cZ6fDLw8mt6bn6br4pi9 ECZQMFvBmQ775l+iVSF/OlHqfK9785wLDd3XOxdxDHMBBlZY8uXHl9rMz6Cst8Wt CrBYyt6S4zsStJ7RbZ9yKVzKmQUTEe1/0SuvHePjLtEY4gXHXfCT3v9D60Yt1BJI LJRKbzfEpohgvNYnujyGYzlVgGdfTWES1STzo/mljmof5XfWm0D54e4aRItKETpd yx9ADjWMp12bHKQF/xDJ39/xsUn/6srRP6+OqcDxfhpNsZSwCQo= =834I -----END PGP SIGNATURE----- --Fig2xvG2VGoz8o/s--