| From: | Shital A <brightuser2019(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Urgent :: Postgresql streaming replication issue - sync mode |
| Date: | 2019-10-02 18:28:06 |
| Message-ID: | CAMp7vw_A7rMTenPqc_NpqTPoMXtcGgeWreHBza5gKis-imXYNQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello,
We are seeing a strange issue with postgresql streaming application in sync
mode.
We are using postgresql 9.6. Old version because of some specific
requirements. We have setup cluster with master-standby using pacemaker.
When we kill master using killall -9 postgres. The failed primary has few
records extra than standby node. We have done setup with synchronous_commit
= remote_apply and have set synchronous_standby_names=server_name.
As the failed primary is having more data, How is it possible that primary
is committing transaction before they were applied on standby with
synchronous_commit=remote_apply?
Please share if you have any thoughts. Are we missing any config ?
Thanks !
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ravi Krishna | 2019-10-02 18:38:35 | Re: Urgent :: Postgresql streaming replication issue - sync mode |
| Previous Message | Tom Lane | 2019-10-02 17:21:51 | Re: Possible bug: SQL function parameter in window frame definition |