Fri Apr 11 07:54:26 PDT 2014
- Previous message: [Slony1-bugs] [Bug 338] cant add column using slonik and execute_script
- Next message: [Slony1-bugs] [Bug 340] New: invalid input for txid_snapshot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=339 Summary: Using binary copy format for sl_log data transfer Product: Slony-I Version: devel Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: jan at wi3ck.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 It was suggested by Peter Goeghegan that Slony could eventually use a binary copy to transport the sl_log data. The binary copy protocol is using network byte order and since the schema of the sl_log_1/sl_log_2 tables within one cluster will always be identical, even across different PostgreSQL versions and architectures, this should actually create no problems. I have no idea how much (or little) of a performance improvement that may result in. But it is worth investigating. -- 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 338] cant add column using slonik and execute_script
- Next message: [Slony1-bugs] [Bug 340] New: invalid input for txid_snapshot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list