| From: | Greg Williamson <gwilliamson39(at)yahoo(dot)com> |
|---|---|
| To: | Edson Richter <edsonrichter(at)hotmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: dropdb breaks replication? |
| Date: | 2012-10-31 22:47:57 |
| Message-ID: | 1351723677.94106.YahooMailNeo@web125905.mail.ne1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Edson --
>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?
>
Sorry for the slow response -- as others have indicated, the drop db is probably not the problem. We have one system that drops a several-gig database hourly and the replication has never failed. We see issues on the master with dead file handles but the replication itself is rock solid.
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Burton | 2012-10-31 22:54:53 | role does not exist |
| Previous Message | Moshe Jacobson | 2012-10-31 21:17:21 | Re: Delay streaming replication using a paramter |