Andres Freund 1b86c81d2d Fix decoding of MULTI_INSERTs when rows other than the last are toasted.
When decoding the results of a HEAP2_MULTI_INSERT (currently only
generated by COPY FROM) toast columns for all but the last tuple
weren't replaced by their actual contents before being handed to the
output plugin. The reassembled toast datums where disregarded after
every REORDER_BUFFER_CHANGE_(INSERT|UPDATE|DELETE) which is correct
for plain inserts, updates, deletes, but not multi inserts - there we
generate several REORDER_BUFFER_CHANGE_INSERTs for a single
xl_heap_multi_insert record.

To solve the problem add a clear_toast_afterwards boolean to
ReorderBufferChange's union member that's used by modifications. All
row changes but multi_inserts always set that to true, but
multi_insert sets it only for the last change generated.

Add a regression test covering decoding of multi_inserts - there was
none at all before.

Backpatch to 9.4 where logical decoding was introduced.

Bug found by Petr Jelinek.
2014-07-06 15:58:01 +02: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-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

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.