Horton

Re: Sync Rep and shutdown Re: Sync Rep v19

Aidan Van Dyk <aidan@highrise.ca>

View thread
From: Aidan Van Dyk <aidan@highrise.ca>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Dimitri Fontaine <dimitri@2ndquadrant.fr>, Simon Riggs <simon@2ndquadrant.com>, Fujii Masao <masao.fujii@gmail.com>, Yeb Havinga <yebhavinga@gmail.com>, Jaime Casanova <jaime@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-03-17T00:53:28Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Document guc context values, and reference them from the config doc section.

On Wed, Mar 16, 2011 at 8:30 PM, Robert Haas <robertmhaas@gmail.com> wrote:

> I think the most important part of all this is that it is logged.
> Anyone who is running synchronous replication should also be doing
> careful monitoring; if not, shame on them, because if your data is
> important enough that you need synchronous replication, it's surely
> important enough to watch the logs.  If you don't, all sorts of bad
> things can happen to your data (either related to sync rep, or
> otherwise) and you'll have no idea until it's far too late.

+++++

If your data is that important, your logs/monitoring are *equally*
important, because they are what give you confidence your data is as
safe as you think it is...


-- 
Aidan Van Dyk                                             Create like a god,
aidan@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.