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 1kVKO7-0000Rf-Rs for pgsql-admin@arkaria.postgresql.org; Wed, 21 Oct 2020 20:07:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kVKO6-0006vm-Fv for pgsql-admin@arkaria.postgresql.org; Wed, 21 Oct 2020 20:07:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kVKO5-0006vf-Ch for pgsql-admin@lists.postgresql.org; Wed, 21 Oct 2020 20:07:10 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kVKO0-0001Ss-Is for pgsql-admin@postgresql.org; Wed, 21 Oct 2020 20:07:08 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 628AC5C0055; Wed, 21 Oct 2020 16:07:02 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 21 Oct 2020 16:07:02 -0400 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=v2M1CSO6qrq01YEiT gkdsnK/C6p26wuDkRrI9bLzqlQ=; b=TEwiOWZ/H9tKdr0YFpaQfhXoKQm19Y1Hs nHTmd8EVEMTztMA+LJLnYPWsk2VwrFbLfFNek33g1cdYcasFzl1CficBwvK2Iolj +XB/a2oVf4YUVuqKTvsVcirxgir6icWytByH1k19H1XAdY5xUJd2kK+pptwaK42q LWK2SR8AuLywUQB93w+hx4wwif3jbmcBBT5qHtSgxauWyRkjFgDjU9aVjL5gSaYP 1k/jO7TSXmDzyfHjoW7hqrxWEAKUe8ihLWqt2r2/yBfzgpQShfbKBkL3vTVKJVhl kGk2U7sb/3tmXM27uDDqLkiys8oUsFLwgYMbXBJC4W9zzHhI9fvLA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrjeehgddugeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggujggfsehmtderredtredvnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpeeigefhleeuudehgedtkeejheeuffdvudejgfetudeikeej hfdufeegfeeivdejteenucfkphepudeltddrleehrdduledrudegkeenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghl vhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.148]) by mail.messagingengine.com (Postfix) with ESMTPA id B30753280066; Wed, 21 Oct 2020 16:07:01 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 287DC2A150F; Wed, 21 Oct 2020 17:06:59 -0300 (-03) Date: Wed, 21 Oct 2020 17:06:59 -0300 From: Alvaro Herrera To: Tom Lane Cc: Wells Oliver , Stephen Frost , pgsql-admin Subject: Re: Odd pg dump error: cache lookup failure Message-ID: <20201021200659.GA32358@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline In-Reply-To: <2762819.1598385063@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 --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2020-Aug-25, Tom Lane wrote: > Oh wait a second. Matviews can have indexes, and getTables doesn't > lock them (because we don't allow LOCK TABLE on views). Here's a quick patchset that makes pg_dump do LOCK TABLE on all relations it dumps; patch 0001 allows server-side LOCK TABLE to run on any relkind, and then 0002 makes pg_dump test for that capability at connection start, and if it exists, then it's used for all relations to dump. --vkogqOf2sHV7VnPd Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0001-accept-any-relkind-in-LOCK-TABLE.patch"