On 13 April 2012 19:15, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
> Robert Haas <robertmhaas@gmail.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