Horton
Menu

Re: Why we lost Uber as a user

Geoff Winkless <pgsqladmin@geoff.dj>

View thread
From: Geoff Winkless <pgsqladmin@geoff.dj>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2016-07-28T10:58:45Z
Lists: pgsql-hackers 
On 27 July 2016 at 17:04, Bruce Momjian <bruce@momjian.us> wrote:

> Well, their big complaint about binary replication is that a bug can
> spread from a master to all slaves, which doesn't happen with statement
> level replication.


​
​I'm not sure that that makes sense to me. If there's a database bug that
occurs when you run a statement on the master, it seems there's a decent
chance that that same bug is going to occur when you run the same statement
on the slave.

Obviously it depends on the type of bug and how identical the slave is, but
statement-level replication certainly doesn't preclude such a bug from
propagating.​


​Geoff​

Commits

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

  1. Advance backend's advertised xmin more aggressively.

  2. Improve snapshot manager by keeping explicit track of snapshots.