| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Add new replication mode synchronous_commit = 'write'. |
| Date: | 2012-04-13 19:16:28 |
| Message-ID: | CAA-aLv72SFqttii7seT0AFn4rCwuQDmGMqFDRuURWz4+grYSXg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 13 April 2012 19:15, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> In my view, remote_write seems a lot more clear than write
>
> +1
>
> I sure didn't understand it to mean remote_write when I read the
> subject line.
Whatever this option value is named, it needs to be referenced in the
postgresql.conf comment for this option, as it isn't currently.
I have a question though. What happens when this is set to "write"
(or "remote_write" as proposed) but it's being used on a standalone
primary? At the moment it's not documented what level of guarantee
this would provide.
--
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2012-04-13 19:57:58 | Re: [COMMITTERS] pgsql: Add new replication mode synchronous_commit = 'write'. |
| Previous Message | Peter Eisentraut | 2012-04-13 18:39:16 | pgsql: Rename bytea_agg to string_agg and add delimiter argument |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-04-13 19:21:48 | Re: PREPARE TRANSACTION compatibility? |
| Previous Message | Robert Haas | 2012-04-13 19:15:28 | Re: Patch: add timing of buffer I/O requests |