pgsql: pg_dump: Move connection-setup code to a separate function.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: pg_dump: Move connection-setup code to a separate function.
Date: 2012-01-27 16:01:19
Message-ID: E1RqoEp-0003bQ-2o@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

pg_dump: Move connection-setup code to a separate function.

Parallel dump will need to repeat these steps for each new connection,
so it's better to have this logic in its own function.

Extracted (with some changes) from a much larger patch
by Joachim Wieland.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/e43166a557d5f28aa66fa15be12fdc6a8ebe380a

Modified Files
--------------
src/bin/pg_dump/pg_dump.c | 139 ++++++++++++++++++++++++---------------------
1 files changed, 74 insertions(+), 65 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2012-01-27 16:26:02 pgsql: Initialize the new bgwriterLatch field properly.
Previous Message Peter Geoghegan 2012-01-27 14:43:12 Re: pgsql: Make bgwriter sleep longer when it has no work to do, to save el