lp:slony-i

Created by Stuart Bishop and last modified
Get this branch:
bzr branch lp:slony-i

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Stuart Bishop
Project:
Slony-I
Status:
Development

Import details

Import Status: Failed

This branch is an import of the HEAD branch of the Git repository at git://git.postgresql.org/git/slony1-engine.git.

The import has been suspended because it failed 5 or more times in succession.

Last successful import was .

Import started on alnitak and finished taking 15 seconds — see the log
Import started on alnitak and finished taking 15 seconds — see the log
Import started on alnitak and finished taking 15 seconds — see the log
Import started on russkaya and finished taking 25 seconds — see the log

Recent revisions

2068. By Steve Singer <email address hidden>

Merge pull request #10 from markstos/remove-summersault

remove typo'ed, expired copyright.

2067. By Steve Singer <email address hidden>

Add support for PG10

PostgreSQL 10 does away with the old convention of $MAJOR.$MINOR.$PATCH

The existing version detection parsing code does not deal with the new
convention. Update the configure check, the slonik check and the slon check
to work with the new convention and continue to work with the old one.

2066. By Steve Singer <email address hidden>

failover unit test improvements

2065. By Steve Singer <email address hidden>

Fix segfault introduced by the previous failover
fixes

2064. By Steve Singer <email address hidden>

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

2063. By Steve Singer <email address hidden>

Add unit test for multi-node failover (cascaded) issues

2062. By Steve Singer <email address hidden>

Fix issues with FAILOVER
In particular it is possible when doing a multi-node failover
with a cascaded node for the result after the failover to
have nodes with a self subscription, a row in sl_subscribe
with the provider and receiver equal.

In fixing that issue we also discovered that slon was not
reloading the set origin's into memory following a FAILOVER
command. This could mean that we were processing SYNC events
from a node which without realizing that node now is the origin
for a set.

2061. By Steve Singer <email address hidden>

Explicitly disallow createEvent and data changes in the same transaction.

The same transaction should not have both a row in sl_event and log data
to sl_log_1 or sl_log_2 with the logTrigger. This is not something slonik
would ever do, and the data changes that the logTrigger logs might not get
replicated as part of the event processing(ie for many non SYNC events).
it is also unclear what order the data should be applied in with respect to
the actions of the non-SYNC event.

2060. By Steve Singer <email address hidden>

add release notes for slonik_build_env now supporting
multiple -schema options.
Thanks Marc Cousin <email address hidden>

2059. By Marc Cousin <email address hidden>

Support multi-schema in slonik_build_env

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.

Subscribers