Re: pdf saving into DB vs. saving file location ? - Mailing list pgsql-general

From Bill Moran
Subject Re: pdf saving into DB vs. saving file location ?
Date
Msg-id 20110323160544.768af7bc.wmoran@potentialtech.com
Whole thread Raw
In response to pdf saving into DB vs. saving file location ?  (Emi Lu <emilu@encs.concordia.ca>)
Responses Re: pdf saving into DB vs. saving file location ?  (Andrew Sullivan <ajs@crankycanuck.ca>)
List pgsql-general
In response to Emi Lu <emilu@encs.concordia.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/

pgsql-general by date:

Previous
From: Emi Lu
Date:
Subject: pdf saving into DB vs. saving file location ?
Next
From: Devrim GÜNDÜZ
Date:
Subject: Re: pdf saving into DB vs. saving file location ?