Re: Where to store Blobs?

From: Jamesie Pic <jpic(at)yourlabs(dot)org>
To: Tim Cross <theophilusx(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Where to store Blobs?
Date: 2019-04-20 00:54:37
Message-ID: CAC6Op19=NG9C61RqwDshhSZkm66Tsp+AyK-a5wukY+7ApbeDig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I forgot to mention that my deployments include automated migrations as
often as possible, sometimes destructive for refactoring purpose, as such,
to maintain PostgreSQL on a basic linux box I am:

- for having an automated backup prior in the automated deployment script
that may play destructive migrations,
- against the needless overhead of coupling both binary and relational data
in operations that slows the whole thing down or makes it less reliable

Also got supposedly many new points against, mixed with more detail on the
points briefly exposed in my previous email, going deeper in detail, about
how it fits in the big picture of my personal practice ... and how this has
destabilized my prod for months:
https://blog.yourlabs.org/post/184290880553/storing-hd-photos-in-a-relational-database-recipe

tl;dr
If you store media files in PostgreSQL on a production server, then do take
disk space alarms seriously even if they happen only during backups.
Otherwise I fail to see how to avoid a pattern of recurring incidents,
"manually unblocking automated deployments" (double debt interest cost
because also defeats the purpose of automating deployment), when not
filling up a disk during the nightly backup dump ...

Hope this helps,

Have a great day

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Morris de Oryx 2019-04-20 12:27:35 Re: Where to store Blobs?
Previous Message Adrian Klaver 2019-04-19 21:41:57 Re: Primary key data type: integer vs identity