Fri May 27 08:25:19 PDT 2011
- Previous message: [Slony1-bugs] [Bug 216] New: monitor threads don't work on Win32
- Next message: [Slony1-bugs] [Bug 216] monitor threads don't work on Win32
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=216 Christopher Browne <cbbrowne at ca.afilias.info> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|slony1-bugs at lists.slony.inf |ssinger at ca.afilias.info |o | Status|NEW |ASSIGNED --- Comment #1 from Christopher Browne <cbbrowne at ca.afilias.info> 2011-05-27 08:25:19 PDT --- I agree with your ordering; #1 seems most preferable, and #3 seems least undesirable. Does this involve using a #define to determine how the timestamp is generated? I suspect so... -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 216] New: monitor threads don't work on Win32
- Next message: [Slony1-bugs] [Bug 216] monitor threads don't work on Win32
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list