Re: pg_dump LOCK TABLE ONLY question - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_dump LOCK TABLE ONLY question
Date
Msg-id CA+TgmoYtSWG+WzfKNtmy9+ZROywqs1vnPEEhQq1=SruN=3KZWw@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump LOCK TABLE ONLY question  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: pg_dump LOCK TABLE ONLY question  (Filip Rembiałkowski <filip.rembialkowski@gmail.com>)
List pgsql-hackers
On Thu, Oct 15, 2015 at 9:13 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> OTOH, now that the catalog is MVCC capable, do we even still need to lock
> the objects for a schema-only dump?

Yes.  The MVCC snapshots used for catalog reads are stable only for
the duration of one particular catalog read.  We're not using the
transaction snapshot.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Improve the concurency of vacuum full table and select statement on the same relation
Next
From: Robert Haas
Date:
Subject: buildfarm failures on crake and sittella