| From: | Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk> |
|---|---|
| To: | pgsql-general(at)PostgreSQL(dot)org |
| Subject: | Re: Best practice for file storage? |
| Date: | 2010-01-31 11:40:01 |
| Message-ID: | hk3q6h$nab$1@pye-srv-01.telemetry.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Joe Kramer wrote:
> Hi,
>
> I need to store a lot of large files (thousands of 10-100 MB files)
> uploaded through my web application and I find that storing them in
> database as bytea field is not practical for backup purposes.
> My database has full backup performed every 12 hours and backup is
> encrypted and copied to server on another continent. Having all the
> heavy binary data in database will make backups impossible.
>
> So I am thinking of having a table just for metadata and file id
> sequence and storing the file on file system:
Wasn't one of the particle accelerator establishments using PostgreSQL
in this way for their raw data?
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Besogonov | 2010-01-31 13:06:41 | Re: Ability to 'fork' a running transaction? |
| Previous Message | Joe Kramer | 2010-01-31 10:46:29 | Best practice for file storage? |