| From: | Anthony <osm(at)inbox(dot)org> |
|---|---|
| To: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
| Cc: | Rod <cckramer(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Storing many big files in database- should I do it? |
| Date: | 2010-04-28 00:45:43 |
| Message-ID: | m2n71cd4dd91004271745z3d75b328z258e1a5818f1779b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Apr 27, 2010 at 5:17 AM, Cédric Villemain <
cedric(dot)villemain(dot)debian(at)gmail(dot)com> wrote:
> store your files in a filesystem, and keep the path to the file (plus
> metadata, acl, etc...) in database.
>
What type of filesystem is good for this? A filesystem with support for
storing tens of thousands of files in a single directory, or should one play
the 41/56/34/41563489.ext game?
Are there any open source systems which handle keeping a filesystem and
database in sync for this purpose, or is it a wheel that keeps getting
reinvented?
I know "store your files in a filesystem" is the best long-term solution.
But it's just so much easier to just throw everything in the database.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryan Murphy | 2010-04-28 01:33:09 | Re: Postgresql on EC2/EBS in production? |
| Previous Message | zhong ming wu | 2010-04-27 23:00:49 | Re: invalid abstime to timestamp error only on specific date range |