| From: | chris kim <chrisk(at)propaas(dot)com> |
|---|---|
| To: | "pgsql-in-general(at)postgresql(dot)org" <pgsql-in-general(at)postgresql(dot)org> |
| Subject: | standby stop replicating, then picked back up |
| Date: | 2017-11-07 20:04:18 |
| Message-ID: | 1583e06e-8391-1763-8d01-2a3c8c3b0b9d@propaas.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-in-general |
Hello,
I had a standby hang for a while, not replicating, but then it fixed
itself but I'm not sure why it happened in the first place. What would I
look into to see why this happened, or any insight into why is greatly
appreciated.
Thanks,
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | chris kim | 2017-11-07 20:08:40 | Fwd: standby stop replicating, then picked back up |
| Previous Message | John R Pierce | 2017-11-07 18:07:40 | Re: Incremental refresh - Materialized view |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | chris kim | 2017-11-07 20:08:40 | Fwd: standby stop replicating, then picked back up |
| Previous Message | Iaam Onkara | 2017-11-05 19:03:27 | How to insert Tamper-proof non-repudiation records in PostgreSQL |