Postgres Pro
Downloads
Home   >   mailing lists

Re: Index on (fixed size) bytea value - Mailing list pgsql-performance

From David G. Johnston
Subject Re: Index on (fixed size) bytea value
Date
Msg-id CAKFQuwYT=k3bLEQCHpYOcSHGS_R5BhW2tkaEPLOduqzdRSu6ZQ@mail.gmail.com
Whole thread Raw
In response to Index on (fixed size) bytea value  (Les <nagylzs@gmail.com>)
Responses Re: Index on (fixed size) bytea value  (Les <nagylzs@gmail.com>)
List pgsql-performance
Tree view
On Mon, Jun 19, 2023 at 1:05 PM Les <nagylzs@gmail.com> wrote:
AFAIK PostgreSQL does not allow a row to occupy multiple blocks.

Your plan is going to heavily involve out-of-band storage.  Please read up on it here:


I'm not looking for a definitive answer, just trying to get some hints from more experienced users before I fill up the drives with terabytes of data.


Store a hash (and other metadata, like the hashing algorithm) as well as the path to some system better designed for object storage and retrieval instead.

David J.

pgsql-performance by date:

Previous
From: Les
Date:
Subject: Index on (fixed size) bytea value
Next
From: Tomas Vondra
Date:
Subject: Re: Merge David and Goliath tables efficiently