LOG: invalid record length at : wanted 24, got 0

Hello, We are seeing an interesting STANDBY behavior, that’s happening once in 3-4 days. The standby suddenly disconnects from the primary, and it throws the error “LOG: invalid record length at : wanted 24, got0”. And then it tries to restore the WAL file from the archive. Due to low write a

Re: LOG: invalid record length at : wanted 24, got 0

Thanks Bharath for your response, > You mentioned that > the connection to primary was lost, so you need to dive deep as to why > it got lost. If the connection was lost half-way through fetching the > WAL record, the standby may emit such a LOG message. The connection was lost due to bad network

How to get accurate backup end time when it is taken from synchronous standby ?

Greetings, When we take backups from a synchronous standby replica, how can we get the accurate timestamp of the backup end time ? (As backup history files are not generated on standbys) For example: this is a part of control file after a backup (created using wal-g by calling pg_startbackup a

Any way to get timestamp from LSN value ?

Hello, Is there any way to get the timestamp of the transaction using LSN value ? For example: can we use the minimum recovery ending location in pg control file to get the minimum recovery timestamp ? Minimum recovery ending location: 28/28000B68 Thanks in advance, Best, Harinath.