Replica max_lag in DSN table

Registered by Martijn Smidt on 2012-08-23

when using the option --recursion-method=dsn make it possible to have a max-lag per recursion. this will make it possible to not wait on slowslaves or backup slaves which may possibly fall behind. if no max-lag is given fallback to the default.

The table would then look like this:
CREATE TABLE `dsns` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `parent_id` int(11) DEFAULT NULL,
  `dsn` varchar(255) NOT NULL,
  `max-lag` int(11) NULL,
  PRIMARY KEY (`id`)
);

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.