Tom Lane c29aff959d Consistently declare timestamp variables as TimestampTz.
Twiddle the replication-related code so that its timestamp variables
are declared TimestampTz, rather than the uninformative "int64" that
was previously used for meant-to-be-always-integer timestamps.
This resolves the int64-vs-TimestampTz declaration inconsistencies
introduced by commit 7c030783a, though in the opposite direction to
what was originally suggested.

This required including datatype/timestamp.h in a couple more places
than before.  I decided it would be a good idea to slim down that
header by not having it pull in <float.h> etc, as those headers are
no longer at all relevant to its purpose.  Unsurprisingly, a small number
of .c files turn out to have been depending on those inclusions, so add
them back in the .c files as needed.

Discussion: https://postgr.es/m/26788.1487455319@sss.pgh.pa.us
Discussion: https://postgr.es/m/27694.1487456324@sss.pgh.pa.us
2017-02-23 15:57:08 -05:00
..
2017-02-06 11:33:58 +02:00
2017-02-06 11:33:58 +02:00
2017-02-06 11:33:58 +02:00
2017-01-17 14:06:07 -05:00
2017-02-06 11:33:58 +02:00
2017-02-22 12:05:42 +05:30
2017-02-06 11:33:58 +02:00
2017-02-06 11:33:58 +02:00
2017-02-06 11:33:58 +02:00
2017-02-06 11:33:58 +02:00
2017-02-06 11:33:58 +02:00
2017-02-06 12:04:04 +02:00
2017-02-06 11:33:58 +02:00
2016-09-15 14:42:29 +03:00
2017-02-06 11:33:58 +02:00
2017-01-03 13:48:53 -05:00
2017-02-06 11:33:58 +02:00
2017-02-13 11:06:11 -05: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.