Re: RFC: PostgreSQL Storage I/O Transformation Hooks

From: Konstantin Knizhnik <knizhnik(at)garret(dot)ru>
To: assam258(at)gmail(dot)com, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, sawada(dot)mshk(at)gmail(dot)com, Tatsuo Ishii <ishii(at)postgresql(dot)org>
Subject: Re: RFC: PostgreSQL Storage I/O Transformation Hooks
Date: 2025-12-28 18:59:04
Message-ID: fd0fe833-09ca-436d-8293-638e0afd9f5d@garret.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 28/12/2025 5:25 PM, Henson Choi wrote:
> Subject: Re: RFC: PostgreSQL Storage I/O Transformation Hooks
>
> Hi Zsolt,
>
> Thank you for your detailed questions. I'll address each point:
>
> 1. Bundling WAL and Buffer Manager
>
> WAL and heap pages are simply different representations of the same
> underlying data. Protecting only one side would be cryptographically
> incomplete; an attacker could bypass encryption by reading the
> unprotected side. Therefore, they must be treated as a single atomic
> unit of protection.

I am not expert in cryptography, better say I even dummy in this area.
But I have one concern about proposed WAL encryption (record level
encryption).
Content of some WAL records can be almost completely predicated (it
contains no user data,
just some Postgres internal data which can be easily reconstructed).
I wonder if this fact can significantly simplify task of cracking cypher?
May be it is safer to use page level encryption for WAL also?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2025-12-28 19:15:23 Re: index prefetching
Previous Message Tomas Vondra 2025-12-28 18:18:30 Re: index prefetching