pg_repack

History

Masahiko Sawada d83ee3d6a0 Change trigger type to AFTER trigger.

During repacking table, if a transaction executes INSERT CONFLICT
ON UPDATE/DO NOTHING, because we define BEFORE trigger on target
table, the contents of operation log table becomes inconsistent
easliy. As a result, pg_reapck fails with a high probability.

To resolve this issue, this changes the trigger type from BEFORE
to AFTER. We define AFTER trigger that is the first of the AFTER
trigger to fire on the table.

2017-01-19 16:32:54 +09:00

init-extension.out

Move regression tests from ./bin/ to ./regress/

2013-05-09 21:15:48 -04:00

init-legacy.out

Move regression tests from ./bin/ to ./regress/

2013-05-09 21:15:48 -04:00

issue3.out

Move regression tests from ./bin/ to ./regress/

2013-05-09 21:15:48 -04:00

plpgsql.out

Move regression tests from ./bin/ to ./regress/