Re: pg 8.3 replication causing corruption

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Bob Hatfield <bobhatfield(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg 8.3 replication causing corruption
Date: 2011-10-12 21:23:05
Message-ID: CA+U5nM+GbhkOH4KUCMXKPWXbDuaKx_W2UXBw=5_RDczrosX0rw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Oct 11, 2011 at 12:12 AM, Bob Hatfield <bobhatfield(at)gmail(dot)com> wrote:

> Should replication cause corruption on the secondary when stopping/starting
> the primary?  (pg 8.3.12, windows 2008 R2 on both servers)

No, it shouldn't. Any duplicate keys would represent a serious error.

It sounds like you're using warm standby, but when you say run
pg_start_backup() AFTER each nightly backup I admit to being confused.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bob Hatfield 2011-10-12 21:30:00 Are file system level differential/incremental backups possible?
Previous Message Simon Riggs 2011-10-12 21:23:02 Re: Using constraint exclusion with 2 floats