Re: Temporary file access API

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: John Morris <john(dot)morris(at)crunchydata(dot)com>
Cc: Antonin Houska <ah(at)cybertec(dot)at>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: Temporary file access API
Date: 2022-10-12 05:55:50
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Sep 27, 2022 at 04:22:39PM +0000, John Morris wrote:
> I’m also wondering about code simplification vs a more general
> encryption/compression framework. I started with the current
> proposal, and I’m also looking at David Steele’s approach to
> encryption/compression in pgbackrest. I’m beginning to think we
> should do a high-level design which includes encryption/compression,
> and then implement it as a “simplification” without actually doing
> the transformations.

It sounds to me like the proposal of this thread is not the most
adapted thing, so I have marked it as RwF as this is the status of 2~3
weeks ago.. If you feel that I am wrong, feel free to scream after

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 2022-10-12 05:56:02 RE: test_decoding assertion failure for the loss of top-sub transaction relationship
Previous Message Michael Paquier 2022-10-12 05:51:53 Re: Allow pageinspect's bt_page_stats function to return a set of rows instead of a single row