Mon May 15 11:30:58 PDT 2017
- Previous message: [Slony1-commit] Slony-I-commit Add unit test for multi-node failover (cascaded) issues
- Next message: [Slony1-commit] Slony-I-commit Fix segfault introduced by the previous failover
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Further changes related to 'Explicitly disallow createEvent and data changes in the same transaction' Add in support where the logApply trigger inserst data into a table that has trigger ,which runs on the replica,that then inserts data into another replicated table. The logApply trigger might have already been called in this transaction but the logTrigger is then called in the same transaction. We then need to setup the plans for inserting data into sl_log_1 or sl_log_2 Branch ------ master Details ------- https://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=ef15a34f71e62bb27471981bbda78f526a08a93e Modified Files -------------- src/backend/slony1_funcs.c | 58 +++++++++++++++++++++++++++++++++++++++------- 1 file changed, 49 insertions(+), 9 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit Add unit test for multi-node failover (cascaded) issues
- Next message: [Slony1-commit] Slony-I-commit Fix segfault introduced by the previous failover
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list