| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: dropdb breaks replication? |
| Date: | 2012-10-31 18:42:56 |
| Message-ID: | 50917130.2050506@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/31/12 11:34 AM, Edson Richter wrote:
> Sorry for the portguese text. Yes, your assumption is correct: WAL
> segment has been excluded before being able to replicate.
> I keep 80 WAL segments, but I was wondering if a drop database is
> being logged: it's just so fast, I thought it wasn't logged.
> And what is the purpose to log (and replicate) the database drop, if
> you will not be able to recover it - IMHO, dropdb should be replicated
> as "database deactivation" or something more or like that...
WAL is not a 'redo' log like Oracle uses.
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
| From | Date | Subject | |
|---|---|---|---|
| Next Message | craig | 2012-10-31 19:59:49 | Unable to do a mailing list proper search |
| Previous Message | Edson Richter | 2012-10-31 18:41:00 | Re: dropdb breaks replication? |