Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ckrkm-0001f9-Qd for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Mar 2017 12:28:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ckrkm-0005ZR-8W for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Mar 2017 12:28:40 +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 1ckrkk-0005Y2-SB for pgsql-hackers@postgresql.org; Mon, 06 Mar 2017 12:28:39 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ckrkh-0007SZ-Jl for pgsql-hackers@postgresql.org; Mon, 06 Mar 2017 12:28:37 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 8F964206B8; Mon, 6 Mar 2017 07:28:34 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Mon, 06 Mar 2017 07:28:34 -0500 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-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=ObPs8UEzlfQ9JvN4wgiZt7QiByQ=; b=Ob+jfLvo3offKARJRDHo kGOrjPVtWFB9BbAKTmfLjogkg9fwX+rVTm1UmipBRJ3E92/+DVV8JapNKFQampLa BpkBvOLuxKmKqy4nZQyV7v5pe3nKo/5D1cYfeOkMv47rccAYOMy1W8Y+gjBOuHXq UczrnYnb5uAmpVfq/fkVtqM= X-ME-Sender: X-Sasl-enc: HpendOFDRX6qwP07kayCGJ4balX4aL+tg5h7s0erfyvC 1488803314 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 46D0E24132; Mon, 6 Mar 2017 07:28:34 -0500 (EST) Subject: Re: Change in "policy" on dump ordering? To: Michael Banck References: <87866740-ef55-8a6d-6480-499b92aa23c0@BlueTreble.com> <8f64786e-824d-7c0d-33a6-3d9e1c8e9fde@2ndquadrant.com> <33b25c65-94f1-6ff6-c717-61a56294a255@2ndquadrant.com> <75409fb1-bd96-25c2-f6b0-c24e28ed2684@2ndquadrant.com> <65049c27-96bf-317b-b435-931f6041f94c@BlueTreble.com> <67d35333-ef65-074a-b2be-52440f245e43@2ndquadrant.com> <753dcafc-a648-9041-e9ca-e405cd4498f4@2ndquadrant.com> <20170306083342.GA8374@nighthawk.caipicrew.dd-dns.de> Cc: Jim Nasby , Pg Hackers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <2605f6d0-8444-528e-4e38-6b13968cfeb7@2ndquadrant.com> Date: Mon, 6 Mar 2017 07:28:33 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170306083342.GA8374@nighthawk.caipicrew.dd-dns.de> Content-Type: text/plain; charset=windows-1252 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 3/6/17 03:33, Michael Banck wrote: > Would this be a candidate for backpatching, or is the behaviour change > in pg_dump trumping the issues it solves? Unless someone literally has a materialized view on pg_policy, it wouldn't make a difference, so I'm not very keen on bothering to backpatch this. -- 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