Bug 298 - Log shipping in 2.2.0 b4 does not ship EXECUTE SCRIPT data
Summary: Log shipping in 2.2.0 b4 does not ship EXECUTE SCRIPT data
Status: RESOLVED FIXED
Alias: None
Product: Slony-I
Classification: Unclassified
Component: slony_logshipper (show other bugs)
Version: devel
Hardware: PC Linux
: low enhancement
Assignee: Slony Bugs List
URL:
Depends on:
Blocks:
 
Reported: 2013-07-03 13:47 UTC by Steve Singer
Modified: 2013-07-10 10:28 UTC (History)
1 user (show)

See Also:

Attachments
fixes + tests for bug298 + doc updates (11.12 KB, patch)
2013-07-04 08:49 UTC, Steve Singer 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Singer 2013-07-03 13:47:40 UTC 
When using a log shipping node in slony 2.2.0 b4 
If you do 
EXECUTE SCRIPT(event node=1,  SQL='alter table sname add column name text;');

The DDL shows up in the .sql files generated for the log shipping nodes but the
ALTER TABLE never executes on the log shipping targets.

The problem is that the apply trigger included in slony1_dump.sh does not have a case for DDL scripts (type 'S')
Comment 1 Steve Singer 2013-07-04 08:49:43 UTC 
Created attachment 169 [details]
fixes + tests for bug298 + doc updates

A patch to fix this issue + make the log shipping unit test try DDL
https://github.com/ssinger/slony1-engine/tree/bug298