Best practice for file storage?

Поиск
Список
Период
Сортировка
От Joe Kramer
Тема Best practice for file storage?
Дата
Msg-id b4c00a111001310246u2cdc99b5h44321763da2a6945@mail.gmail.com
обсуждение исходный текст
Ответы Re: Best practice for file storage?  (Mark Morgan Lloyd <markMLl.pgsql-general@telemetry.co.uk>)
Re: Best practice for file storage?  (Craig Ringer <craig@postnewspapers.com.au>)
Re: Best practice for file storage?  (Andy Colson <andy@squeakycode.net>)
Re: Best practice for file storage?  (Steve Atkins <steve@blighty.com>)
Список pgsql-general
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:

CREATE TABLE business_logo
(
  file_id bigserial NOT NULL,
 file_name varchar,
 file_date timestamp,
);

Storing file in path composed from serial id, e.g. file with id 2345
will be stored in
/webapp/files/2/3/4/5/2345

So I can backup files separately and database backup is still quick
and painless.

This is very simplistic and straightforward method.
I suppose there are better ways of doing it, using some virtual file system?
Anyone had a similar issue with avoiding of storing large files in
database, how did you solve it?

Thanks.

В списке pgsql-general по дате отправления:

Предыдущее
От: Craig Ringer
Дата:
Сообщение: Re: Ability to 'fork' a running transaction?
Следующее
От: Mark Morgan Lloyd
Дата:
Сообщение: Re: Best practice for file storage?