| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Odd pg dump error: cache lookup failure |
| Date: | 2020-10-21 20:06:59 |
| Message-ID: | 20201021200659.GA32358@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-accept-any-relkind-in-LOCK-TABLE.patch | text/x-diff | 1.0 KB |
| 0002-pg_dump-lock-all-rels-not-just-RELKIND_RELATION.patch | text/x-diff | 3.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-10-21 20:33:54 | Re: Odd pg dump error: cache lookup failure |
| Previous Message | hubert depesz lubaczewski | 2020-10-15 13:49:11 | Re: Regarding query on the postgresql upgrade |