From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | emilu(at)encs(dot)concordia(dot)ca |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pdf saving into DB vs. saving file location ? |
Date: | 2011-03-23 20:05:44 |
Message-ID: | 20110323160544.768af7bc.wmoran@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to Emi Lu <emilu(at)encs(dot)concordia(dot)ca>:
> Hello list,
>
> A question about saving PDF (size around 160kb) into postgresql large
> object columns vs. saving into a directory.
>
> May I know the performance differences? Pros and crons please?
>
> Each year, 20 new pdfs will be saved into DB (each around 160KB).
We store a WHOLE lot more binary data in our DBs than that. The
big advantage to us is that we store the data in TEXT fields, and
use Slony to replicate it, so in the event of hardware failure, we
don't have to worry about the DB looking for data that isn't on
the file server.
Never measured the actual performance difference, but we haven't
had any performance issues with keeping the data in the DB. I'm
sure keeping it on the filesystem is faster, though.
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GÜNDÜZ | 2011-03-23 20:10:59 | Re: pdf saving into DB vs. saving file location ? |
Previous Message | Emi Lu | 2011-03-23 20:01:55 | pdf saving into DB vs. saving file location ? |