From: Matheus Alcantara <matheusssilv97@gmail.com>
To: Smolkin Grigory <smallkeen@gmail.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: clog segment truncation
Date: Mon, 10 Nov 2025 10:43:47 -0300
Message-ID: <DE525BYLM6ZC.1BA8B3U2H9H1Z@gmail.com> (raw)
In-Reply-To: <CAMp+ueZkG+HTWd0tajG4nDU_Vk51+wkngtuq7XjOjEBEW7t8Gw@mail.gmail.com>
References: <CAMp+ueZkG+HTWd0tajG4nDU_Vk51+wkngtuq7XjOjEBEW7t8Gw@mail.gmail.com>
On Mon Nov 10, 2025 at 9:29 AM -03, Smolkin Grigory wrote:
> So is it possible that either all_frozen bit was set incorrectly or wansn't
> unset when tuples were created?
> I will be happy to provide any additional information if required.
> PostgreSQL version: 15.6, data_checksums: on
>
Actually the 15.6 is quite old. I would also recommend to upgrade to the
latest 15 release which is 15.14.
I didn't find any specific release note about clog truncation but you
are missing some important fixes though.
There is this fix [1] on 15.8 but I'm not sure if it's fully related
with your issue faced here.
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c809a2b2d
--
Matheus Alcantara
EDB: http://www.enterprisedb.com
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: pgsql-bugs@postgresql.org
Cc: matheusssilv97@gmail.com, smallkeen@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: clog segment truncation
In-Reply-To: <DE525BYLM6ZC.1BA8B3U2H9H1Z@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox