Peter Eisentraut a33969ee91 pg_standby: Remove code for .backup files
These files are no longer requested on recovery (since
06f82b29616cd9effcaefd99c6b6e2e80697482f), so the code for handling them
here is useless.

Author: Yugo Nagata <nagata@sraoss.co.jp>
2018-07-01 15:10:08 +02:00
..
2018-04-26 14:47:16 -04:00
2018-01-02 23:30:12 -05:00
2017-09-19 15:31:37 -04:00
2018-04-26 14:47:16 -04:00
2018-01-02 23:30:12 -05:00
2017-09-14 22:22:59 -04:00
2017-11-08 11:37:28 -05:00
2018-01-02 23:30:12 -05:00
2017-03-30 14:18:53 -04:00
2018-04-26 14:47:16 -04:00
2018-01-02 23:30:12 -05:00
2017-06-21 15:35:54 -04:00
2018-01-02 23:30:12 -05:00
2018-04-26 14:47:16 -04:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2017-06-21 15:35:54 -04:00
2018-04-03 09:47:18 -04:00

The PostgreSQL contrib tree
---------------------------

This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly
because they address a limited audience or are too experimental to be
part of the main source tree.  This does not preclude their
usefulness.

User documentation for each module appears in the main SGML
documentation.

When building from the source distribution, these modules are not
built automatically, unless you build the "world" target.  You can
also build and install them all by running "make all" and "make
install" in this directory; or to build and install just one selected
module, do the same in that module's subdirectory.

Some directories supply new user-defined functions, operators, or
types.  To make use of one of these modules, after you have installed
the code you need to register the new SQL objects in the database
system by executing a CREATE EXTENSION command.  In a fresh database,
you can simply do

    CREATE EXTENSION module_name;

See the PostgreSQL documentation for more information about this
procedure.