Tom Lane 82bbb60c30 Fix valgrind warning for btree_gist indexes on macaddr.
The macaddr opclass stores two macaddr structs (each of size 6) in an
index column that's declared as being of type gbtreekey16, ie 16 bytes.
In the original coding this led to passing a palloc'd value of size 12
to the index insertion code, so that data would be fetched past the
end of the allocated value during index tuple construction.  This makes
valgrind unhappy.  In principle it could result in a SIGSEGV, though
with the current implementation of palloc there's no risk since
the 12-byte request size would be rounded up to 16 bytes anyway.

To fix, add a field to struct gbtree_ninfo showing the declared size of
the index datums, and use that in the palloc requests; and use palloc0
to be sure that any wasted bytes are cleanly initialized.

Per report from Andres Freund.  No back-patch since there's no current
risk of a real problem.
2014-05-16 15:11:51 -04:00
..
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-01-07 16:05:30 -05:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-01-13 15:43:29 +02:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-01-07 16:05:30 -05:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-15 13:23:31 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-01-07 16:05:30 -05:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-05-06 12:12:18 -04:00
2014-03-03 16:32:18 -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.