| From: | Lonni J Friedman <netllama(at)gmail(dot)com> |
|---|---|
| To: | Joseph Marlin <jmarlin(at)saucontech(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: WAL Replication Working but Not Working |
| Date: | 2013-08-21 18:23:26 |
| Message-ID: | CAP=oouEESE7dV16pCA=j9NhhnnJz05VefnbFQ+wqd1kF9VVm+g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
The first thing to do is look at your server logs around the time when
it stopped working.
On Wed, Aug 21, 2013 at 7:08 AM, Joseph Marlin <jmarlin(at)saucontech(dot)com> wrote:
> We're having an issue with our warm standby server. About 9:30 last night, it stopped applying changes it received in WAL files that are shipped over to it as they are created. It is still reading WAL files as they delivered, as the startup_log.txt shows, but the changes in the primary database aren't actually being made to the standby, and haven't been since last night.
>
> Is there any way we can figure out what is going on here? We'd like to recover somehow without having to restore from a base backup, and we'd like to figure out what is happening so we can prevent it in the future.
>
> Thanks!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | carlosinfl . | 2013-08-21 19:55:05 | PostgreSQL 9.2 Logging |
| Previous Message | Ivan Radovanovic | 2013-08-21 17:46:02 | Unique constraint and unique index |