Use SET TRANSACTION READ ONLY in pg_dump, if server supports it.
This currently does little except serve as documentation. (The one case
where it has a performance benefit, SERIALIZABLE mode in 9.1 and up, was
already using READ ONLY mode.) However, it's possible that it might have
performance benefits in future, and in any case it seems like good
practice since it would catch any accidentally non-read-only operations.
Pavan Deolasee
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/26d905a12dda783783c60cec04decb00cd2e67f4
Modified Files
--------------
src/bin/pg_dump/pg_dump.c | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
