Re: Practical usage of large objects.

From: Thomas Markus <t(dot)markus(at)proventis(dot)net>
To:
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Practical usage of large objects.
Date: 2020-05-14 18:30:53
Message-ID: 6fa45071-faae-5c43-9ae4-ed32fb232035@proventis.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Am 14.05.20 um 15:36 schrieb Laurenz Albe:
> 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
We used lo a lot in a project for large uploads (>4GB files). Really
useful in a cloud environment.

I was interested in speed camparison myself and made a similar test with
network connection and without pg specific code.
https://github.com/5UtJAjiRWj1q/psql-lob-performance

File access is really fast and lo access is much slower than bytea (as
expected). But content size limitation and memory consumption for bytea
is problematic.

regards
Thomas

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-05-14 18:46:18 Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?
Previous Message Eduard Rozenberg 2020-05-14 18:27:58 Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?