Skip to content

Copy protocol 22 - #1

Open
cbbrowne wants to merge 8 commits into
wieck:copy-protocol-22from
cbbrowne:copy-protocol-22
Open

Copy protocol 22#1
cbbrowne wants to merge 8 commits into
wieck:copy-protocol-22from
cbbrowne:copy-protocol-22

Conversation

@cbbrowne

Copy link
Copy Markdown
Collaborator

FYI, here's some cleanups that amount to opening up development on v2.2.

It includes a draft of release notes that includes our discussion of ~2 weeks ago about what needs to happen at upgrade time from 2.[^2] to 2.2.

Jan Wieck and others added 7 commits October 14, 2011 17:27
1) Change the sl_log_N tables adding columns for the table schema and name;
   Add a special column for update actions, containing the number of updated
   columns for the SET clause;
   Change log_cmddata into log_cmdargs of type text[].

   This includes a check script in the ./tools directory that can be
   used to verify that a cluster is completely caught up as well as the
   changes to upgradeSchema() to change the sl_log_N format during a
   Slony version upgrade. This worked for a 2.0 -> 2.2 upgrade.

   Still needs documentation of the upgrade procedure.

2) Adjust the log triggers to produce the new log format.

3) Remove the slon remote_worker code that updates the replicated user
   tables. The above changes broke that part anyway and this allows for
   an apply trigger to take over the work of applying data changes.

extra) Added a PL/pgSQL implementation of the apply trigger. This results
   in a fully functional slony system again and acts as a proof of concept.
@cbbrowne

cbbrowne commented Nov 2, 2011

Copy link
Copy Markdown
Collaborator Author

Note, patch 7510458 resolves the problem that running UPDATE FUNCTIONS fails due to trying to add apply_trigger a second time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant