Re: dropdb breaks replication?

From: Lonni J Friedman <netllama(at)gmail(dot)com>
To: Edson Richter <edsonrichter(at)hotmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: dropdb breaks replication?
Date: 2012-10-31 17:39:54
Message-ID: CAP=oouGTJuthjJOeaj-Px1QKbvJtAaaxvaViNFdCNwmz+fLp6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Oct 31, 2012 at 10:32 AM, Edson Richter
<edsonrichter(at)hotmail(dot)com> wrote:
> I've two PostgreSQL 9.1.6 running on Linux CentOS 5.8 64bit.
> They are replicated asynchronously.
>
> Yesterday, I've dropped a database of 20Gb, and then replication has broken,
> requiring me to manually synchronize both servers again.
>
> It is expected that dropdb (or, perhaps, createdb) break existing
> replication between servers?

How did you determine that replication was broken, and how did you
manually synchronize the servers? Are you certain that replication
was working prior to dropping the database?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Edson Richter 2012-10-31 18:01:26 Re: dropdb breaks replication?
Previous Message Edson Richter 2012-10-31 17:32:19 dropdb breaks replication?