Re: Index on (fixed size) bytea value

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





David G. Johnston <david.g.johnston@xxxxxxxxx> ezt írta (időpont: 2023. jún. 19., H, 22:30):
On Mon, Jun 19, 2023 at 1:05 PM Les <nagylzs@xxxxxxxxx> 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 aware of the TOAST, and how it works. I was referring to it ("I think that it should be as large as possible, without hitting the toast. ") I have designed a separate "block" table specifically to avoid storing binary data in the TOAST. So my plan is not going to involve out-of-band storage.

Just to make this very clear: a record in the block table would store a block, not the whole file. My question is to finding the optimal block size (without hitting the toast), and finding the optimal hash algorithm for block de-duplication.

Unless I totally misunderstood how the TOAST works. (?)
   
    Laszlo

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux