On 18.03.14 02:32, Joe Conway wrote:
> On 03/17/2014 05:55 PM, Jeff Janes wrote:
>> On Mon, Mar 17, 2014 at 5:48 PM, Craig Ringer
>>
>> LOCK TABLE table1, table2, table3, ...
>
>> would help, instead of doing individual statements?
>
>> If I recall correctly, someone did submit a patch to do th
On 18.03.14 00:15, Tom Lane wrote:
> Jim Nasby writes:
>> On 3/17/14, 8:47 AM, Tom Lane wrote:
>>> (Note that this is only one of assorted O(N^2) behaviors in older versions
>>> of pg_dump; we've gradually stamped them out over time.)
>
>> On that note, it's recommended that when you are taking a
patch against github/master as I can manage
(and I didn't use C for a long time). I hope you find it useful.
regards,
Jürgen Strobel
commit 393d47cf6b5ce77297e52e7fc390aa862fd2c2fd
Author: Jürgen Strobel
Date: Fri Mar 7 16:54:22 2014 +0100
Add option --no-table-locks to pg_dump.
diff -
