Re: pg_dump LOCK TABLE ONLY question

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump LOCK TABLE ONLY question
Date: 2015-10-01 23:19:53
Message-ID: CAB7nPqRgxtzC5igdatU9y0bHEgbc3Oubv2yFw5xVEKvVNyjP7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 1, 2015 at 10:43 PM, Filip Rembiałkowski
<filip(dot)rembialkowski(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-10-01 23:19:57 Re: ON CONFLICT issues around whole row vars,
Previous Message Andres Freund 2015-10-01 23:17:48 Re: ON CONFLICT issues around whole row vars,