Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ayIOS-0004XI-On for pgsql-hackers@arkaria.postgresql.org; Thu, 05 May 2016 12:28:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ayIOR-00060X-91 for pgsql-hackers@arkaria.postgresql.org; Thu, 05 May 2016 12:28:35 +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.84_2) (envelope-from ) id 1ayIOQ-00060Q-Ju for pgsql-hackers@postgresql.org; Thu, 05 May 2016 12:28:34 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ayIOM-00042P-KL for pgsql-hackers@postgresql.org; Thu, 05 May 2016 12:28:33 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id F2AE420395 for ; Thu, 5 May 2016 08:28:27 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 05 May 2016 08:28:27 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=8PDcrfEvQ/XbDq1 7H2WgvFIX58I=; b=clBz6cIW0DIjdvBPYSz7k2gIwEf4HAQUavs84cJT6AOL3yn ARTFVQIAaTmw+gxCiXRiAf4tQxdNRs6y4vwVnFS6H6RXVusWxbBpGwAoIKfhoSnh YMJ4sCrd1So0mBsHLBhXTbBsiRg2sPwWQjTRuk2fP2TYz1KBqiVWEiqtaJY0= X-Sasl-enc: we+B01p7EHYu1FU9dVttoD95QAIyiAdt2rioB42wltRY 1462451307 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id A9C6F68026B; Thu, 5 May 2016 08:28:27 -0400 (EDT) Subject: Re: pg_dump vs. TRANSFORMs To: Tom Lane References: <20160504183952.GE10850@tamriel.snowman.net> <0a288671-29ec-ecdd-d8ae-e0f5c73dcc8d@2ndquadrant.com> <15548.1462418615@sss.pgh.pa.us> Cc: Stephen Frost , pgsql-hackers@postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <376f5fb1-85cb-6b4c-9927-645b5e209456@2ndquadrant.com> Date: Thu, 5 May 2016 08:28:27 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <15548.1462418615@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 5/4/16 11:23 PM, Tom Lane wrote: > Actually, I believe it will be dumped. selectDumpableCast believes it > should dump casts with OID >= FirstNormalObjectId. That's a kluge no > doubt, but reasonably effective; looks like we've been doing that since > 9.0. > > pg_dump appears not to have a special-case selectDumpableTransform > routine. Instead it falls back on the generic selectDumpableObject > for transforms. That's a bad idea because the only useful bit of > knowledge selectDumpableObject has is to look at the containing > namespace ... and transforms don't have one, just as casts don't. > > My recommendation is to clone that cast logic for transforms. Hmm. The way I understand it is that Stephen wants to make dumping that test case work. But note that that test case is bogus; it wouldn't actually do anything useful in practice. There aren't any functions in the system catalog that could be used for actual transforms. So making these changes in pg_dump isn't really of much practical value. Perhaps it would be easier to change the test case or adjust the testing procedure? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers