| From: | Wolfgang Keller <feliphil(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | SQL DATALINK (Re: Storing large files in multiple schemas: BLOB or BYTEA) |
| Date: | 2012-10-15 12:38:43 |
| Message-ID: | 20121015143843.2882f017dc510e5b4adcbe93@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > I need to store large files (from several MB to 1GB) in Postgres
> > database. The database has multiple schemas. It looks like Postgres
> > has 2 options to store large objects: LOB and BYTEA. However we seem
> > to hit problems with each of these options.
>
> I believe the general consensus around here is to not do that, if you
> can avoid it. File systems are much better equipped to handle files
> of that magnitude, especially when it comes to retrieving them,
> scanning through their contents, or really, any access pattern aside
> from simple storage.
>
> You're better off storing the blob on disk somewhere and storing a
> row that refers to its location. Either key pieces for a naming
> scheme or the full path.
What's the state of implementation (planning) for this?:
http://wiki.postgresql.org/wiki/DATALINK
Sincerely,
Wolfgang
| From | Date | Subject | |
|---|---|---|---|
| Next Message | P. Broennimann | 2012-10-15 12:54:05 | NOTIFY/LISTEN in Postgresql |
| Previous Message | lst_hoe02 | 2012-10-15 11:30:09 | Re: WebSphere Application Server support for postgres |