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 1i86fY-0002WF-L2 for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Sep 2019 17:44:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i86fW-0001j2-79 for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Sep 2019 17:44:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i86fV-0001cH-1F for pgsql-hackers@lists.postgresql.org; Wed, 11 Sep 2019 17:44:37 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1i86fN-00038k-SZ for pgsql-hackers@lists.postgresql.org; Wed, 11 Sep 2019 17:44:35 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 39376591 for ; Wed, 11 Sep 2019 13:44:27 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 11 Sep 2019 13:44:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=pa/aL9azqGSs3/y+TmKMwimdUvX9QVcISRDLcXKk4ko=; b=mg0qmjgC /fB399atv3//M0gI4J4G0wFahtg5p1jHLbSy4x6s0JXCygzHgL2HtArQSDWRC3hy 6G7bg2FhgTTVL5OxEa19ZaI+k8bK2fmo+19ktmCJ1bVS9j8k8ACQCfMBYF6VxXDM 3jSXoeve58rSXsc3eaXV9PoY3OTuV72d05Nh/mrVA0qC9edJC6JZPsmcgQtKOw5d LSCloppui+kr1oBeS/SrRxgfTodV37Lf7sppcg/pnG7Q5f7BueRxM6YHS5Wv/1gy 5zRsDbpMNGUwUV9GTQMSoOP/FIYBz8HqhYWcA1E98CXzn3EhOxlnIbuRzVSNo2KY m5NGwL3fygOQCQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrtdefgdeltdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkgggtugfgjggfsehtkeertddtredunecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcufhhrohhmucdvnhgusfhurggurhgrnhhtuceorghlvhhhvghrrh gvsegrlhhvhhdrnhhoqdhiphdrohhrgheqnecuffhomhgrihhnpedvnhguqhhurggurhgr nhhtrdgtohhmnecukfhppeduledtrdduvddurddvledrfeenucfrrghrrghmpehmrghilh hfrhhomheprghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrghenucevlhhushht vghrufhiiigvpedt X-ME-Proxy: Received: from nimloth.alvh.no-ip.org (unknown [190.121.29.3]) by mail.messagingengine.com (Postfix) with ESMTPA id 58CCFD6005D for ; Wed, 11 Sep 2019 13:44:26 -0400 (EDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id C6A1912099A; Wed, 11 Sep 2019 14:44:23 -0300 (-03) Date: Wed, 11 Sep 2019 14:44:23 -0300 From: Alvaro Herrera from 2ndQuadrant To: Pg Hackers Subject: Re: propagating replica identity to partitions Message-ID: <20190911174423.GA28675@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201902042353.r3aqj2cx4hvz@alvherre.pgsql> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I've not had time to work on this issue, and there are a few remaining problems in the patch; mostly that I will need to change the way pg_dump represents the replica identity so that it is only defined when the index is dumped in all partitions rather than immediately after creating the index. Also, the bug reported by Dmitry Dolgov. So I'm marking this as Returned with Feedback, with the intention to resubmit for November. Thanks, -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services