From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Add new replication mode synchronous_commit = 'write'. |
Date: | 2012-01-24 20:35:22 |
Message-ID: | CAJKUy5iCx2vm5ogMEm5eGTHjb45q-gvaSf0n+-o2X39HanE37g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Tue, Jan 24, 2012 at 3:22 PM, Simon Riggs <simon(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-01-25 02:51:21 | pgsql: Fix new SQL tablespace location function usage in pg_upgrade to |
Previous Message | Simon Riggs | 2012-01-24 20:22:57 | pgsql: Add new replication mode synchronous_commit = 'write'. |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-01-24 20:53:48 | some longer, larger pgbench tests with various performance-related patches |
Previous Message | Simon Riggs | 2012-01-24 20:28:25 | Re: New replication mode: write |