pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Odd pg dump error: cache lookup failure
Date: Tue, 25 Aug 2020 15:51:03 -0400
Message-ID: <2762819.1598385063@sss.pgh.pa.us> (raw)
In-Reply-To: <2762015.1598384009@sss.pgh.pa.us>
References: <CAOC+FBXosgRbSi-A+VLP8t5pmErEnP3M8aRJJ1z5HcyhvQM_eA@mail.gmail.com>
	<20200824231338.GA30623@alvherre.pgsql>
	<20200824231621.GA29590@tamriel.snowman.net>
	<2748788.1598376276@sss.pgh.pa.us>
	<CAOC+FBXXq_iDU9iFHUoL5F8PY8pZawiLQ1xuPq3VW9_RJcN0JQ@mail.gmail.com>
	<2760667.1598382327@sss.pgh.pa.us>
	<CAOC+FBVmcNR5d09YdNc_NG=b5_Y7OQmqbznJcGAt37U3wJxwpQ@mail.gmail.com>
	<2762015.1598384009@sss.pgh.pa.us>

I wrote:
> Wells Oliver <wells.oliver@gmail.com> writes:
>> And refreshing materialized views during the dump process wouldn't cause
>> this?

> matviews can't be part of inheritance trees AFAIR, so we'd need some
> other theory to explain it that way.

Oh wait a second.  Matviews can have indexes, and getTables doesn't
lock them (because we don't allow LOCK TABLE on views).  So it's fairly
clear that you could get here with no lock if 1152770777 is a matview.
However, it's still not entirely clear how a refresh could trigger
the observed error.  We certainly aren't changing the matview's OID
when we do that.  Do we rewrite the pg_attribute entries anyway?
And even if we do, why would there be a problem?

Are your refreshes using CONCURRENTLY?

			regards, tom lane





view thread (24+ messages)  latest in thread

Message-ID: <2762819.1598385063@sss.pgh.pa.us>
Permalink:  ../2762819.1598385063@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2762819.1598385063@sss.pgh.pa.us

 · 

reply
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: tgl@sss.pgh.pa.us, wells.oliver@gmail.com, sfrost@snowman.net, alvherre@2ndquadrant.com
  Subject: Re: Odd pg dump error: cache lookup failure
  In-Reply-To: <2762819.1598385063@sss.pgh.pa.us>

* 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