pg_test_fsync(1) [centos man page]

PG_TEST_FSYNC(1)					  PostgreSQL 9.2.7 Documentation					  PG_TEST_FSYNC(1)

NAME

       pg_test_fsync - determine fastest wal_sync_method for PostgreSQL

SYNOPSIS

       pg_test_fsync [option...]

DESCRIPTION

       pg_test_fsync is intended to give you a reasonable idea of what the fastest wal_sync_method is on your specific system, as well as
       supplying diagnostic information in the event of an identified I/O problem. However, differences shown by pg_test_fsync might not make any
       difference in real database throughput, especially since many database servers are not speed-limited by their transaction logs.

OPTIONS

       pg_test_fsync accepts the following command-line options:

       -f, --filename
	   Specifies the file name to write test data in. This file should be in the same file system that the pg_xlog directory is or will be
	   placed in. (pg_xlog contains the WAL files.) The default is pg_test_fsync.out in the current directory.

       -s, --secs-per-test
	   Specifies the number of seconds for each test. The more time per test, the greater the test's accuracy, but the longer it takes to run.
	   The default is 2 seconds, which allows the program to complete in about 30 seconds.

       -V, --version
	   Print the pg_test_fsync version and exit.

       -?, --help
	   Show help about pg_test_fsync command line arguments, and exit.

AUTHOR

       Bruce Momjian <bruce@momjian.us>

SEE ALSO

       postgres(1)

PostgreSQL 9.2.7						    2014-02-17							  PG_TEST_FSYNC(1)

PG_CONFIG(1)						  PostgreSQL Client Applications					      PG_CONFIG(1)

NAME

       pg_config - retrieve information about the installed version of PostgreSQL

SYNOPSIS

       pg_config { --bindir | --includedir | --includedir-server | --libdir | --pkglibdir | --configure | --version }...

DESCRIPTION

       The  pg_config utility prints configuration parameters of the currently installed version of PostgreSQL. It is intended, for example, to be
       used by software packages that want to interface to PostgreSQL to facilitate finding the required header files and libraries.

OPTIONS

       To use pg_config, supply one or more of the following options:

       --bindir
	      Print the location of user executables. Use this, for example, to find the psql program. This is normally also  the  location  where
	      the pg_config program resides.

       --includedir
	      Print the location of C header files of the client interfaces.

       --includedir-server
	      Print the location of C header files for server programming.

       --libdir
	      Print the location of object code libraries.

       --pkglibdir
	      Print  the  location  of dynamically loadable modules, or where the server would search for them. (Other architecture-dependent data
	      files may also be installed in this directory.)

       --configure
	      Print the options that were given to the configure script when PostgreSQL was configured for building.  This can be used	to  repro-
	      duce  the  identical  configuration, or to find out with what options a binary package was built. (Note however that binary packages
	      often contain vendor-specific custom patches.)

       --version
	      Print the version of PostgreSQL and exit.

       If more than one option (except for --version) is given, the information is printed in that order, one item per line.

NOTES

       The option --includedir-server is new in PostgreSQL 7.2. In prior releases, the server include files were installed in the same location as
       the  client  headers,  which could be queried with the --includedir. To make your package handle both cases, try the newer option first and
       test the exit status to see whether it succeeded.

       In releases prior to PostgreSQL 7.1, before the pg_config came to be, a method for finding the equivalent configuration information did not
       exist.

HISTORY

       The pg_config utility first appeared in PostgreSQL 7.1.

SEE ALSO

       PostgreSQL Programmer's Guide

Application							    2002-11-22							      PG_CONFIG(1)