From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Wells Oliver <wells.oliver@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Odd pg dump error: cache lookup failure
Date: Wed, 21 Oct 2020 17:06:59 -0300
Message-ID: <20201021200659.GA32358@alvherre.pgsql> (raw)
In-Reply-To: <2762819.1598385063@sss.pgh.pa.us>
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.
Attachments:
0001-accept-any-relkind-in-LOCK-TABLE.patch (text/x-diff, 0B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, wells.oliver@gmail.com, sfrost@snowman.net
Subject: Re: Odd pg dump error: cache lookup failure
In-Reply-To: <20201021200659.GA32358@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox