From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Only issue LOCK TABLE commands when necessary |
Date: | 2016-05-06 18:06:59 |
Message-ID: | E1ayk9T-0000To-2M@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Only issue LOCK TABLE commands when necessary
Reviewing the cases where we need to LOCK a given table during a dump,
it was pointed out by Tom that we really don't need to LOCK a table if
we are only looking to dump the ACL for it, or certain other
components. After reviewing the queries run for all of the component
pieces, a list of components were determined to not require LOCK'ing
of the table.
This implements a check to avoid LOCK'ing those tables.
Initial complaint from Rushabh Lathia, discussed with Robert and Tom,
the patch is mine.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/e1b120a8cbb0f39a79926fd173f33e57202cdfa0
Modified Files
--------------
src/bin/pg_dump/pg_dump.c | 5 ++++-
src/bin/pg_dump/pg_dump.h | 27 +++++++++++++++++++++++++++
2 files changed, 31 insertions(+), 1 deletion(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-05-06 18:40:43 | pgsql: Use mul_size when multiplying by the number of parallel workers. |
Previous Message | Peter Eisentraut | 2016-05-06 18:02:57 | pgsql: Update config.guess and config.sub |