From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dmitry Igrishin <dmitigr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Practical usage of large objects. |
Date: | 2020-05-14 03:59:49 |
Message-ID: | 20200514035949.GD166343@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, May 13, 2020 at 01:55:48PM -0400, Tom Lane wrote:
> Dmitry Igrishin <dmitigr(at)gmail(dot)com> writes:
>> As you know, PostgreSQL has a large objects facility [1]. I'm curious
>> are there real systems which are use this feature?
>
> We get questions about it regularly, so yeah people use it.
I recall that some applications where I work make use of it for some
rather large log-like data. At the end of the day, it really boils
down to if you wish to store blobs of data which are larger than 1GB,
the limit for toasted fields, as LOs can be up to 4TB. Also, updating
or reading a LO can be much cheaper than a toasted field, as the
latter would update/read the value as a whole.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2020-05-14 04:28:40 | Reuse an existing slot with a new initdb |
Previous Message | Michael Paquier | 2020-05-14 03:52:34 | Re: Reuse an existing slot with a new initdb |