Thread: pgsql: Add new replication mode synchronous_commit = 'write'.
Add new replication mode synchronous_commit = 'write'. Replication occurs only to memory on standby, not to disk, so provides additional performance if user wishes to reduce durability level slightly. Adds concept of multiple independent sync rep queues. Fujii Masao and Simon Riggs Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/443b4821f1649bc617c5ce1f6f3ffc65842a8930 Modified Files -------------- doc/src/sgml/config.sgml | 18 +++- doc/src/sgml/high-availability.sgml | 16 +++- src/backend/replication/syncrep.c | 112 ++++++++++++++++++--------- src/backend/replication/walsender.c | 3 +- src/backend/utils/misc/guc.c | 5 +- src/include/access/xact.h | 1 + src/include/replication/syncrep.h | 13 +++- src/include/replication/walsender_private.h | 8 +- 8 files changed, 124 insertions(+), 52 deletions(-)
On Tue, Jan 24, 2012 at 3:22 PM, Simon Riggs <simon@2ndquadrant.com> wrote: > Add new replication mode synchronous_commit = 'write'. > Replication occurs only to memory on standby, not to disk, > so provides additional performance if user wishes to > reduce durability level slightly. Adds concept of multiple > independent sync rep queues. > > Fujii Masao and Simon Riggs > i guess, you should add the new value in postgresql.conf too. just a question, why not add a flush value and make it behave like on? actually sync rep is on in both cases and having the different names makes more easy to unserstand what is happening. i only want to keep on for compatibility but i wouldn't mind if we remove it in favor of more descriptive names. or there's any difference between on and flush that i'm failing to see? -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación