| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: pg_dump LOCK TABLE ONLY question |
| Date: | 2015-10-16 15:06:19 |
| Message-ID: | CA+TgmoYtSWG+WzfKNtmy9+ZROywqs1vnPEEhQq1=SruN=3KZWw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 15, 2015 at 9:13 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-10-16 15:13:00 | buildfarm failures on crake and sittella |
| Previous Message | Robert Haas | 2015-10-16 15:04:51 | Re: Improve the concurency of vacuum full table and select statement on the same relation |