pgsql: Move long_options structures to the top of main() functions, for - Mailing list pgsql-committers

From Bruce Momjian
Subject pgsql: Move long_options structures to the top of main() functions, for
Date
Msg-id E1TeWb2-0003p5-B3@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Move long_options structures to the top of main() functions, for
consistency.

Per suggestion from Tom.

Branch
------
master

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

Modified Files
--------------
contrib/pg_test_fsync/pg_test_fsync.c   |    1 +
contrib/pg_test_timing/pg_test_timing.c |    1 +
contrib/pgbench/pgbench.c               |   18 +++++++-------
src/bin/pg_basebackup/pg_receivexlog.c  |    1 +
src/bin/pg_dump/pg_dumpall.c            |   36 +++++++++++++++---------------
src/test/regress/pg_regress.c           |   14 ++++++------
6 files changed, 37 insertions(+), 34 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Add missing buffer lock acquisition in GetTupleForTrigger().
Next
From: Bruce Momjian
Date:
Subject: pgsql: In pg_upgrade, dump each database separately and use