Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Paquier
Subject Re: pg_dump LOCK TABLE ONLY question
Date
Msg-id CAB7nPqRgxtzC5igdatU9y0bHEgbc3Oubv2yFw5xVEKvVNyjP7Q@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump LOCK TABLE ONLY question  (Filip Rembiałkowski <filip.rembialkowski@gmail.com>)
Responses Re: pg_dump LOCK TABLE ONLY question  (Filip Rembiałkowski <filip.rembialkowski@gmail.com>)
Re: pg_dump LOCK TABLE ONLY question  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tree view 
On Thu, Oct 1, 2015 at 10:43 PM, Filip Rembiałkowski
<filip.rembialkowski@gmail.com> wrote:
> I just want to understand why there is LOCK TABLE not LOCK TABLE ONLY.

It seems to me that you'd still want to use LOCK TABLE particularly if
the dump is only done on a subset of tables, using --table for
example.
--
Michael

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: ON CONFLICT issues around whole row vars,
Next
From: Peter Geoghegan
Date:
Subject: Re: ON CONFLICT issues around whole row vars,