Re: [BUGS] pg_dump(1) failures when concurrently refreshing mat views - Mailing list pgsql-bugs

From Nico Williams
Subject Re: [BUGS] pg_dump(1) failures when concurrently refreshing mat views
Date
Msg-id 20170419212356.GA2844@localhost
Whole thread Raw
In response to Re: [BUGS] pg_dump(1) failures when concurrently refreshing mat views  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] pg_dump(1) failures when concurrently refreshing mat views
List pgsql-bugs
On Wed, Apr 19, 2017 at 05:20:31PM -0400, Tom Lane wrote:
> Nico Williams <nico@cryptonector.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
-- 


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] pg_dump(1) failures when concurrently refreshing mat views
Next
From: "David G. Johnston"
Date:
Subject: Re: [BUGS] BUG #14626: array_agg( anyarray ) unexpected error withmulti-valued single-dimension array