MIME-Version: 1.0
References: 
 <CACG=ezaWg7_nt-8ey4aKv2w9LcuLthHknwCawmBgEeTnJrJTcw@mail.gmail.com>
 <2bc58592-9d74-4af0-bdd1-1a88e8683f7c@iki.fi>
 <CACG=ezZwdvsijzuXE3hex3xHcoz75EQYBXRTsQJVwbo5J5sS3g@mail.gmail.com>
 <CACG=ezbs912S58=uR17b4w8uuWv1=OcCRaTW_OWdFm4+tXZA6w@mail.gmail.com>
 <CAGjGUA+BfcWyccNN4=tHsW_E-koRxbg8h8ut6hjvPsHMgmek6w@mail.gmail.com>
 <CACG=ezYbYO_KHWdeDedbDcY0tOS0JfaqBxG3=bG5+DdsDK4MpQ@mail.gmail.com>
 <CACG=ezYpZRPwoRCz_h3Qerd3XJNdpTHCpwGbZphNdy26tA4_qQ@mail.gmail.com>
 <36531c0e-292c-409d-bbc7-a252cf6e910a@iki.fi>
 <54aa8f65-f0e4-4464-b543-e0399c1cab1e@iki.fi>
 <CACG=ezYUJSvnuxntkURNWo_1vZ+AtmcQfqd_h6WgDzGaudfw+Q@mail.gmail.com>
 <4a9dda70-0af7-41a4-9636-b168f2fc48ef@iki.fi>
 <46cc45e9-fddd-44bc-bcb3-96889aafd921@iki.fi>
 <CAExHW5tUEkiQrvm9hgccjKUNkWBnJ5_HDUrAwiHBTxu+Vuj29Q@mail.gmail.com>
 <6c298bc4-7029-4c1d-bf16-3e094842ce32@iki.fi>
 <9ee6324a-44fc-42fb-bf8e-7c3b53395588@iki.fi>
 <CAPpHfdsMd9TQ8ZbMnStMfFvBoBMwBCSC+8zcOYY9VDMYQzUYyQ@mail.gmail.com>
 <52227f05-51aa-40c4-8f83-9c79fff16175@iki.fi>
In-Reply-To: <52227f05-51aa-40c4-8f83-9c79fff16175@iki.fi>
From: Maxim Orlov <orlovmg@gmail.com>
Date: Wed, 3 Dec 2025 12:54:23 +0300
Message-ID: 
 <CACG=ezY-uzrQvUbm4_txT6hR4r78cgLoXGpT61+OXGodLw=qZA@mail.gmail.com>
Subject: Re: POC: make mxidoff 64 bits
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Alexander Korotkov <aekorotkov@gmail.com>,
 Alvaro Herrera <alvherre@alvh.no-ip.org>,
	wenhui qiu <qiuwenhuifx@gmail.com>,
	Postgres hackers <pgsql-hackers@lists.postgresql.org>,
	Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000002bfab90645093398"
Archived-At: 
 <https://www.postgresql.org/message-id/CACG%3DezY-uzrQvUbm4_txT6hR4r78cgLoXGpT61%2BOXGodLw%3DqZA%40mail.gmail.com>
Precedence: bulk

--0000000000002bfab90645093398
Content-Type: text/plain; charset="UTF-8"

The biggest problem with compression, in my opinion, is that losing
even one byte causes the loss of the entire compressed block in the
worst case scenario. After all, we still don't have checksums for the
SLRU's, which is a shame by itself.

Again, I'm not against the idea of compression, but the risks need to
be considered.

As a software developer, I definitely want to implement compression and
save a few gigabytes. However, given my previous experience using
Postgres in real-world applications, reliability at the cost of several
gigabytes would not have caused me any trouble. Just saying.

-- 
Best regards,
Maxim Orlov.

--0000000000002bfab90645093398
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The biggest problem with compression, in my opinion, is th=
at losing<br>even one byte causes the loss of the entire compressed block i=
n the<br>worst case scenario. After all, we still don&#39;t have checksums =
for the<br>SLRU&#39;s, which is a shame by itself.<br><br>Again, I&#39;m no=
t against the idea of compression, but the risks need to<br>be considered.<=
br><br>As a software developer, I definitely want to implement compression =
and<br>save a few gigabytes. However, given my previous experience using<br=
>Postgres in real-world applications, reliability at the cost of several<br=
>gigabytes would not have caused me any trouble. Just saying.<div><br clear=
=3D"all"></div><span class=3D"gmail_signature_prefix">-- </span><br><div di=
r=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div>Best regards,<br>=
</div><div>Maxim Orlov.</div></div></div></div>

--0000000000002bfab90645093398--