Simon Riggs 96ef3b8ff1 Allow I/O reliability checks using 16-bit checksums
Checksums are set immediately prior to flush out of shared buffers
and checked when pages are read in again. Hint bit setting will
require full page write when block is dirtied, which causes various
infrastructure changes. Extensive comments, docs and README.

WARNING message thrown if checksum fails on non-all zeroes page;
ERROR thrown but can be disabled with ignore_checksum_failure = on.

Feature enabled by an initdb option, since transition from option off
to option on is long and complex and has not yet been implemented.
Default is not to use checksums.

Checksum used is WAL CRC-32 truncated to 16-bits.

Simon Riggs, Jeff Davis, Greg Smith
Wide input and assistance from many community members. Thank you.
2013-03-22 13:54:07 +00:00
..
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-03-10 14:16:02 -04:00
2013-01-01 17:15:01 -05:00
2012-07-16 22:15:03 +03:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-03-17 14:18:33 -04:00
2013-01-01 17:15:01 -05:00
2012-04-23 22:43:09 -04:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2012-12-06 17:47:30 -03:00
2013-02-22 18:56:42 -03:00
2012-04-14 09:29:54 +03: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 "gmake all" and "gmake
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.