From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PDF files: to store in database or not |
Date: | 2016-12-08 15:21:31 |
Message-ID: | 91fea4f4-f72a-0b8f-9de8-9aa2028fa2cb@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/08/2016 07:16 AM, Rich Shepard wrote:
> On Thu, 8 Dec 2016, John DeSoi wrote:
>
>> I have been storing PDFs in Postgres for several years without any
>> problems. Documents range in size from a few pages to 100+ pages. I'm
>> using a bytea column, not large objects. I store the documents in a
>> separate database from the rest of the application data in order to make
>> it easy to exclude in database dumps or backup in some other way. I'm
>> currently managing about 600,000 documents.
>
> John,
>
> This is really good information. Rather than using a separate database I
> think that storing all PDFs in a separate table makes sense for my
> application. Backup practices will be the domain of those using the
> application (which I've decided to open-source and give away because I'm
> not
> in the software business). A simple join to the appropriate data table will
> make them available.
>
> Not having used the bytea data type before I'll read how to work with it.
http://initd.org/psycopg/docs/usage.html?highlight=binary#adapt-binary
>
> Thanks very much for your insights,
>
> Rich
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2016-12-08 15:25:20 | Re: PDF files: to store in database or not |
Previous Message | Charles Clavadetscher | 2016-12-08 15:19:31 | Re: Importing SQLite database |