Re: How to store "blobs" efficiently for small and large sizes, with random access

From: Dominique Devienne <ddevienne(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: How to store "blobs" efficiently for small and large sizes, with random access
Date: 2022-10-20 08:00:08
Message-ID: CAFCRh-_HEi3=B39OU5EiKsXuX5MPqy86iOf_sNnoUkBCetOKMA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Oct 19, 2022 at 5:30 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> That's exactly what I was trying to say.
> If there's no compression, we don't read prior chunks.

Great to read that. I'll probably try to benchmark w/ and w/o
compression eventually.
Need to deal with other issues first, will take a while to report back on this.

> This can be seen in detoast_attr_slice()

Thank you for the pointer. I'll be sure to have a look at that code.
And thanks again for chiming in, with very useful info Alvaro.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dominique Devienne 2022-10-20 08:32:44 Re: How to store "blobs" efficiently for small and large sizes, with random access
Previous Message Dominique Devienne 2022-10-20 07:57:06 Re: How to store "blobs" efficiently for small and large sizes, with random access