Re: WAL file corruption on standby PostgreSQL
От | vrms |
---|---|
Тема | Re: WAL file corruption on standby PostgreSQL |
Дата | |
Msg-id | 0322e728-fe36-45a4-9667-299246028db8@netcologne.de обсуждение исходный текст |
Ответ на | Re: WAL file corruption on standby PostgreSQL (Muhammad Ikram <mmikram@gmail.com>) |
Ответы |
RE: WAL file corruption on standby PostgreSQL
|
Список | pgsql-admin |
On 7/22/24 8:42 PM, Muhammad Ikram wrote:
>> Also try to see what caused corruption of WAL archives.
out of curiosity ... any hint in how to approach this?
>> Also try to see what caused corruption of WAL archives.
out of curiosity ... any hint in how to approach this?
On 7/22/24 8:42 PM, Muhammad Ikram wrote:
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.RegardsMuhammad IkramOn Mon, Jul 22, 2024 at 11:26 PM Wasim Devale <wasimd60@gmail.com> wrote:Hi All2024-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/8183BFA8I got this error and the replication has stopped. Please suggest about invalid resource manager ID.Thanks,Wasim
--Muhammad Ikram
В списке pgsql-admin по дате отправления: