Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fk9Th-0007Ak-Lm for pgsql-admin@arkaria.postgresql.org; Mon, 30 Jul 2018 14:48:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fk9Tg-0008Gg-1L for pgsql-admin@arkaria.postgresql.org; Mon, 30 Jul 2018 14:48:52 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1fk9Tf-0008GZ-QK for pgsql-admin@lists.postgresql.org; Mon, 30 Jul 2018 14:48:51 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fk9Tc-0000Ir-DO for pgsql-admin@lists.postgresql.org; Mon, 30 Jul 2018 14:48:51 +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 w6UEmjM6028008; Mon, 30 Jul 2018 10:48:45 -0400 From: Tom Lane To: Achilleas Mantzios cc: pgsql-admin@lists.postgresql.org Subject: Re: Table's REPLICATE IDENTITY : where is it kept? In-reply-to: <88a346ef-9ec0-ca97-5a15-94529d68cbc2@matrix.gatewaynet.com> References: <1e6cc5ad-b84a-7c07-8c08-a4d0c3cdc938@matrix.gatewaynet.com> <24602.1532957847@sss.pgh.pa.us> <88a346ef-9ec0-ca97-5a15-94529d68cbc2@matrix.gatewaynet.com> Comments: In-reply-to Achilleas Mantzios message dated "Mon, 30 Jul 2018 17:11:01 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28006.1532962125.1@sss.pgh.pa.us> Date: Mon, 30 Jul 2018 10:48:45 -0400 Message-ID: <28007.1532962125@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Achilleas Mantzios writes: > On 30/07/2018 16:37, Tom Lane wrote: >> Really? There's certainly code in there that purports to do it: > When its a plain INDEX it is pg_dump'ed correctly. > But when this is a CONSTRAINT index it is not. Oooh, you're right, dumpIndex() has code for that but dumpConstraint() lacks it. regards, tom lane