public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: Subramanian,Ramachandran <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: AW: how long should Archive logs be retained
Date: Fri, 28 Nov 2025 08:10:49 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Fri, 2025-11-28 at 04:46 +0000, Subramanian,Ramachandran wrote:
> Question >>> Wow !! That is so new to me. So
> 1. if log wrap around happens and some Wal-Files containing uncomitted log records are being overwritten,
No, they are deleted (well, perhaps recycled, but that amounts to the same).
> 2. AND iin the mean time some data updates pertaining to these uncomitted transactions have been flushed from the data buffers to disk
> 3. AND after the data buffers have been flushed the transaction fails ( and I assume releases all the locks )
>
> how does postgres know that a particular unlocked row it finds in the disk ( or even the bufferpool
> for that matter ) is not in a valid state even though it physically exists in the table?
> How can it decode this information?
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: AW: how long should Archive logs be retained
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox