Re: WAL file corruption on standby PostgreSQL

vrms <vrms@xxxxxxxxxxxxx> · Mon, 22 Jul 2024 21:24:50 +0200



    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?

    
    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.
        

        Regards
        Muhammad Ikram
        

        On Mon, Jul 22, 2024 at
          11:26 PM Wasim Devale <wasimd60@xxxxxxxxx>
          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