Re: Practical usage of large objects. - Mailing list pgsql-general

From Laurenz Albe
Subject Re: Practical usage of large objects.
Date
Msg-id 72a02fe6b1b78120136cf7f96cd35c0c2ed2f4d2.camel@cybertec.at
Whole thread Raw
In response to Re: Practical usage of large objects.  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Practical usage of large objects.  (Thomas Markus <t.markus@proventis.net>)
List pgsql-general
On Thu, 2020-05-14 at 12:59 +0900, Michael Paquier wrote:
> On Wed, May 13, 2020 at 01:55:48PM -0400, Tom Lane wrote:
> > Dmitry Igrishin <dmitigr@gmail.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.

Interesting; only recently I played with that a little and found that
that is not necessarily true:

https://www.cybertec-postgresql.com/en/binary-data-performance-in-postgresql/

Yours,
Laurenz Albe




pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Reuse an existing slot with a new initdb
Next
From: Support
Date:
Subject: Re: Reuse an existing slot with a new initdb