Re: pg_dump(1) failures when concurrently refreshing mat views

From: Nico Williams <nico(at)cryptonector(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_dump(1) failures when concurrently refreshing mat views
Date: 2017-04-19 21:23:56
Message-ID: 20170419212356.GA2844@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Apr 19, 2017 at 05:20:31PM -0400, Tom Lane wrote:
> Nico Williams <nico(at)cryptonector(dot)com> writes:
> > pg_dump(1) gets an EXCLUSIVE LOCK with NOWAIT
>
> ... uh, really? It's not supposed to take anything higher than ACCESS
> SHARE, which should coexist fine with anything short of ACCESS EXCLUSIVE.

Whoops, sorry, that's a mistake in drafting the report. You're right,
it takes an ACCESS SHARE MODE lock, NOWAIT. The remainder of the report
remains correct.

Nico
--

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2017-04-19 21:32:07 Re: BUG #14626: array_agg( anyarray ) unexpected error with multi-valued single-dimension array
Previous Message Tom Lane 2017-04-19 21:20:31 Re: pg_dump(1) failures when concurrently refreshing mat views