pgsql: In pg_upgrade, copy fsm, vm, and extent files by checking for fi

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: pgsql-committers@postgresql.org
Date: 2012-11-14T22:32:12Z
Lists: pgsql-hackers
In pg_upgrade, copy fsm, vm, and extent files by checking for file
existence via open(), rather than collecting a directory listing and
looking up matching relfilenode files with sequential scans of the
array.  This speeds up pg_upgrade by 2x for a large number of tables,
e.g. 16k.

Per observation by Ants Aasma.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/29add0de4920e4f448a30bfc35798b939c211d97

Modified Files
--------------
contrib/pg_upgrade/file.c        |   55 ----------
contrib/pg_upgrade/pg_upgrade.h  |    2 -
contrib/pg_upgrade/relfilenode.c |  208 +++++++++++++++-----------------------
3 files changed, 82 insertions(+), 183 deletions(-)

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. In pg_upgrade, copy fsm, vm, and extent files by checking for file