Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kb8hz-0007wa-Ft for pgsql-bugs@arkaria.postgresql.org; Fri, 06 Nov 2020 20:51:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kb8hw-0007Xd-Va for pgsql-bugs@arkaria.postgresql.org; Fri, 06 Nov 2020 20:51:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kb8hw-0007XW-PU for pgsql-bugs@lists.postgresql.org; Fri, 06 Nov 2020 20:51:40 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kb8hq-0000IT-FQ for pgsql-bugs@lists.postgresql.org; Fri, 06 Nov 2020 20:51:39 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 3F7C75C0065; Fri, 6 Nov 2020 15:51:32 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 06 Nov 2020 15:51:32 -0500 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:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=/pJtIct2rSSnY32J6 puWX5btKvLKFHmcnwyxq5cEZHc=; b=qw9mkSvsBj1qGBYoOGbYTfwGezLx/qTas buz91uMFYyS5KA5/Xme/BJ71c3xDC65LpUhpOpAgqTDv8zPLZAaNRWLQ21EWXKZJ xnhsTaTsfrz4at6EPLpJSr1fXkIAzlPhES5y5C9ki8u47psWU0izIZIEQaPFWrpO 0i0oPipUDj1s2g4puRPPVrhbJS0wxFvo+1sVM2M0yiWUvB7G/rOZyfO0xdoPgpN6 OSJphA6ZkdXpdnM0JNys51+OFCtQsY0jofsAuga61pVKTGsE1DXY8f6osjE9JpQl XhLsLKQPmFvg4XWa4ci82gE61uCvhmp3sdD0R9DFku3CuxhZvQmhA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedruddtledgudegiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkgggtuggjfgesthdtredttdervdenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvefgleevgeeujeeghfegteeghfegheeifeehheelteet ieduieeihffggfehffetnecukfhppeduledtrdelhedrudelrddugeeknecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegr lhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.148]) by mail.messagingengine.com (Postfix) with ESMTPA id 7EF3E3060061; Fri, 6 Nov 2020 15:51:31 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id BA0C22A0FDA; Fri, 6 Nov 2020 17:51:28 -0300 (-03) Date: Fri, 6 Nov 2020 17:51:28 -0300 From: Alvaro Herrera To: Tom Lane Cc: Andrew Bille , exclusion@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16703: pg-dump fails to process recursive view definition Message-ID: <20201106205128.GA12433@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1624928.1604694339@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Nov-06, Tom Lane wrote: > > Hm, yeah, so more to do here. (Sure glad we found these issues before > > next week's releases, not after.) > > After some off-list discussion with Alvaro, we're thinking the best way > forward is to revert the pg_dump and LOCK TABLE changes for now, and > try again after next week's releases. Nod. Thanks Andrew for reporting these problems, and thanks Tom for quickly addressing them.