Robert Haas 0518eceec3 Adjust HeapTupleSatisfies* routines to take a HeapTuple.
Previously, these functions took a HeapTupleHeader, but upcoming
patches for logical replication will introduce new a new snapshot
type under which the tuple's TID will be used to lookup (CMIN, CMAX)
for visibility determination purposes.  This makes that information
available.  Code churn is minimal since HeapTupleSatisfiesVisibility
took the HeapTuple anyway, and deferenced it before calling the
satisfies function.

Independently of logical replication, this allows t_tableOid and
t_self to be cross-checked via assertions in tqual.c.  This seems
like a useful way to make sure that all callers are setting these
values properly, which has been previously put forward as
desirable.

Andres Freund, reviewed by Álvaro Herrera
2013-07-22 13:38:44 -04:00
..
2013-01-01 17:15:01 -05:00
2013-01-01 17:15:01 -05:00
2013-05-29 16:58:43 -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-05-29 16:58:43 -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-05-29 16:58:43 -04:00
2013-01-01 17:15:01 -05:00
2013-05-29 16:58:43 -04:00
2013-05-29 16:58:43 -04: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-05-29 16:58:43 -04:00
2013-01-01 17:15:01 -05: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.