| From: | Muhammad Ikram <mmikram(at)gmail(dot)com> |
|---|---|
| To: | Wasim Devale <wasimd60(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: WAL file corruption on standby PostgreSQL |
| Date: | 2024-07-22 18:42:28 |
| Message-ID: | CAGeimVoLwB_Qw6z_0ns4FLarZ_hZXUD-WYUwDBktvJOGfVq0Mg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi Wasim,
IMO, you will have to rebuild the standby server by taking base backup from
Primary and copying it to standby, restart standby. Also try to see what
caused corruption of WAL archives.
Regards
Muhammad Ikram
On Mon, Jul 22, 2024 at 11:26 PM Wasim Devale <wasimd60(at)gmail(dot)com> wrote:
> Hi All
>
> 2024-07-22 11:15:10 PDT [1723]: [7028-1] user=,db=,app=,client= LOG:
> restored log file "000000010000170900000081" from archive
> 2024-07-22 11:15:10 PDT [1723]: [7029-1] user=,db=,app=,client= LOG:
> invalid resource manager ID 128 at 1709/8183BFA8
> 2024-07-22 11:15:10 PDT [1723]: [7030-1] user=,db=,app=,client= LOG:
> invalid resource manager ID 128 at 1709/8183BFA8
>
>
> I got this error and the replication has stopped. Please suggest about invalid
> resource manager ID.
>
> Thanks,
> Wasim
>
--
Muhammad Ikram
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Muhammad Ikram | 2024-07-22 18:51:16 | Re: Oracle to Postgres |
| Previous Message | Wasim Devale | 2024-07-22 18:26:08 | WAL file corruption on standby PostgreSQL |