| From: | Thomas Güttler <guettliml(at)thomas-guettler(dot)de> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Use bytearray for blobs or not? |
| Date: | 2019-01-04 13:15:56 |
| Message-ID: | 01e65f2d-a6cc-871a-e3b8-7f6a70118e59@thomas-guettler.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 04.01.19 um 12:48 schrieb Achilleas Mantzios:
> On 4/1/19 1:41 μ.μ., Thomas Güttler wrote:
>> Some months ago I wrote a little application with Python+Django which stores
>> blob data in bytearrays.
>>
>> It works.
>>
>> In the future there will be a lot more traffic, and I am unsure
>> if this is really a good solution. I know this is more FUD than
>> concrete PG issue.
>>
>> What do you think?
>
> Performance (at least for JDBC) is known to be better with blobs.
> However, with bytea life is just easier for many reasons (backups, logical replication, other types of replication, sys
> management, etc).
I could switch to a s3 like storage server, too. Up to now, this would only be
some lines of code. I could store the s3 IDs in postgres.
--
Thomas Guettler http://www.thomas-guettler.de/
I am looking for feedback: https://github.com/guettli/programming-guidelines
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erika Knihti-Van Driessche | 2019-01-04 14:21:15 | Multiple postgresql clusters with same version and separate binaries |
| Previous Message | Kristjan Tammekivi | 2019-01-04 12:20:55 | Re: Potentially undocumented behaviour change in Postgres 11 concerning OLD record in an after insert trigger |