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

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: 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-19 14:58:40
Message-ID: 0ca2695b-b545-8593-8137-90d6ab6835b9@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/19/22 04:47, Dominique Devienne wrote:
[snip]
> PS: Another drawback of lo is that because it's a single table, it
> still subject to the 32 TB limit on a relation.
> The 4TB limit per lo is way more than we need, but the 32 TB limit
> may actually be more of an issue for
> our larger clients, which have thousands of projects, each with
> upwards of a few millions of those blobs.

Partition the table on the first segment of the Primary Key.  From
experience, anything else can lead to serious query degradation.

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2022-10-19 15:04:10 Re: How to store "blobs" efficiently for small and large sizes, with random access
Previous Message Ron 2022-10-19 14:49:26 Re: Speeding up adding fky on a very large table