| From: | Landry Chedjou <l(dot)chedjou(at)irembo(dot)com> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | Elly Kadenyo <e(dot)kadenyo(at)irembo(dot)com>, Patrick Ndjientcheu <p(dot)ndjientcheu(at)irembo(dot)com> |
| Subject: | Issue faced in production |
| Date: | 2022-11-30 22:26:11 |
| Message-ID: | CAG8uavFZe+0gYk=JyK_uT_vADO_+M5R0Ls49sXS=ky7M5zsLPQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Dear Team,
I trust you are well.
Today, we faced a critical issue on our production cluster Postgresql
version 13
deployed via Zalando Operator inside k8s workloads (01 Master, 02 Replicas).
We faced the issue below
2022-11-30 01:45:18.250 CAT,,,1627043,,6386998e.18d3a3,1,,2022-11-30
01:45:18 CAT,,0,FATAL,XX000,"could not connect to the primary
server: FATAL: the database system is in recovery mode
FATAL: the database system is in recovery mode",,,,,,,,,"","walreceiver"
We had to perform a restoration to be able to get back the platform online.
Currently, we are trying to get more insights on the potential reasons
which might have caused it and find a long solution. We need your guidance
to help to understand better what can cause that.
Thank you so much for being available and for the amazing job you are
doing to make the world open.
Best regards,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-12-01 07:35:32 | BUG #17703: Recursive query early terminate when subquery result of the recursive term is NULL |
| Previous Message | Daniel Gustafsson | 2022-11-29 16:48:47 | Re: BUG #17702: An assert failed in parse_utilcmd.c |