Re: Zstandard support for toast compression

Поиск
Список
Период
Сортировка
Искать
От
Robert Haas
Тема
Re: Zstandard support for toast compression
Дата
в 13:32:15
Msg-id
CA+TgmoZm07cwAxu2mQmPn3Grvw7n7nS5J_H=gk0W=hXVyQZ5JA@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Zstandard support for toast compression Michael Paquier <michael@paquier.xyz>
Re: Zstandard support for toast compression Robert Haas <robertmhaas@gmail.com>
Re: Zstandard support for toast compression Stephen Frost <sfrost@snowman.net>
Re: Zstandard support for toast compression Tom Lane <tgl@sss.pgh.pa.us>
Re: Zstandard support for toast compression Stephen Frost <sfrost@snowman.net>
Re: Zstandard support for toast compression Robert Haas <robertmhaas@gmail.com>
Re: Zstandard support for toast compression Amit Kapila <amit.kapila16@gmail.com>
Re: Zstandard support for toast compression Peter Geoghegan <pg@bowt.ie>
Re: Zstandard support for toast compression Michael Paquier <michael@paquier.xyz>
Re: Zstandard support for toast compression Robert Haas <robertmhaas@gmail.com>
Re: Zstandard support for toast compression Michael Paquier <michael@paquier.xyz>
Re: Zstandard support for toast compression Robert Haas <robertmhaas@gmail.com>
Re: Zstandard support for toast compression Michael Paquier <michael@paquier.xyz>
Re: Zstandard support for toast compression Nikolay Shaplov <dhyan@nataraj.su>
Re: Zstandard support for toast compression Stephen Frost <sfrost@snowman.net>
Re: Zstandard support for toast compression Nikolay Shaplov <dhyan@nataraj.su>
Re: Zstandard support for toast compression Aleksander Alekseev <aleksander@timescale.com>
Re: Zstandard support for toast compression Michael Paquier <michael@paquier.xyz>
Re: Zstandard support for toast compression Robert Haas <robertmhaas@gmail.com>
Re: Zstandard support for toast compression Justin Pryzby <pryzby@telsasoft.com>
On Mon, May 23, 2022 at 12:33 AM Michael Paquier  wrote:
> On Thu, May 19, 2022 at 04:12:01PM -0400, Robert Haas wrote:
> > On Thu, May 19, 2022 at 4:20 AM Michael Paquier  wrote:
> >> Btw, shouldn't we have something a bit more, err, extensible for the
> >> design of an extensible varlena header?  If we keep it down to some
> >> bitwise information, we'd be fine for a long time but it would be
> >> annoying to review again an extended design if we need to extend it
> >> with more data.
> >
> > What do you have in mind?
>
> A per-varlena checksum was one thing that came into my mind.

It's a bit hard for me to believe that such a thing would be
desirable. I think it makes more sense to checksum blocks than datums,
because:

(1) There might be a lot of really small datums, and storing checksums
for all of them could be costly, or
(2) The datums could on the other hand be really big, and then the
checksum is pretty non-specific about where the problem has happened.

YMMV, of course.

-- 
Robert Haas
EDB: http://www.enterprisedb.com


В списке pgsql-hackers по дате отправления
От: Jan Wieck
Дата:
Сообщение: Re: Limiting memory allocation
От: Robert Haas
Дата:
FAQ