| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Pascal Cloup <ptpas059(at)gmail(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: large objects |
| Date: | 2015-06-23 16:49:20 |
| Message-ID: | 20150623164920.GA25365@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Tue, Jun 23, 2015 at 03:33:52PM +0200, Pascal Cloup wrote:
> - use the option WITH OIDS during CREATE TABLE or ALTER TABLE
WITH OIDS is in no way related to storing large blobs in tables, and
generally shouldn't be used.
> Is it a good idea to store such large objects in DB? and if so, what is the
> best choice?
In majority of cases, I would say that, storing binary blobs in database
is bad idea. Waste of resources. It's better store them on filesystem,
and in DB just store path to the file.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pascal Cloup | 2015-06-24 13:43:34 | Fwd: large objects |
| Previous Message | Pascal Cloup | 2015-06-23 13:33:52 | large objects |