Andres Freund 101c7ee3ee Use new overflow aware integer operations.
A previous commit added inline functions that provide fast(er) and
correct overflow checks for signed integer math. Use them in a
significant portion of backend code.  There's more to touch in both
backend and frontend code, but these were the easily identifiable
cases.

The old overflow checks are noticeable in integer heavy workloads.

A secondary benefit is that getting rid of overflow checks that rely
on signed integer overflow wrapping around, will allow us to get rid
of -fwrapv in the future. Which in turn slows down other code.

Author: Andres Freund
Discussion: https://postgr.es/m/20171024103954.ztmatprlglz3rwke@alap3.anarazel.de
2017-12-12 16:55:37 -08:00
..
2017-06-21 15:35:54 -04:00
2017-06-21 15:35:54 -04:00
2017-06-21 15:35:54 -04:00
2017-09-19 15:31:37 -04:00
2017-11-08 11:37:28 -05:00
2017-11-08 11:37:28 -05:00
2017-11-08 11:37:28 -05:00
2017-09-14 22:22:59 -04:00
2017-11-08 11:37:28 -05:00
2017-06-21 15:35:54 -04:00
2017-03-30 14:18:53 -04:00
2017-09-29 11:08:24 -04:00
2017-06-21 15:35:54 -04:00
2017-06-21 15:35:54 -04:00
2017-06-21 15:35:54 -04:00
2017-09-22 11:49:48 -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.