From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Andrew Rose <andrew(dot)rose(at)metaswitch(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Transaction ordering on log-shipping standby |
Date: | 2011-09-20 14:24:45 |
Message-ID: | CA+U5nM+RQnZFGke72CZ1Lew9feVd2RVhc4YqVYxta2TgQhp1Nw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 20, 2011 at 11:46 AM, Andrew Rose
<andrew(dot)rose(at)metaswitch(dot)com> wrote:
> I've got a question about transaction ordering in a log-shipping replication environment.
>
> Here's the setup...
>
> - A pair of PostgreSQL 9 servers in active/standby configuration, using log-shipping
> - A single client, using a single connection
> - The client commits transaction 1
> - The client commits transaction 2
> - The active server fails and the standby is promoted to be the active server
>
> The client re-establishes the connection and is attempting to determine which transactions have made it onto the standby server (and which never made it because of replication delays).
>
> Here's the question...
>
> If the client can confirm that transaction 2 has happened on the standby, does that imply that transaction 1 has also made it onto the standby?
>
> Or to put the question another way, is the ordering of transactions on the active and standby servers guaranteed to be the same?
Yes, the transaction ordering is log serializable because that's the
only way that provably works.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | MirrorX | 2011-09-20 14:30:14 | upgrade postgres to 8.4.8, centos 5.3 |
Previous Message | Vincent de Phily | 2011-09-20 14:12:44 | Re: Seeing foreign key lookups in explain output |