Re: PDF files: to store in database or not

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: PDF files: to store in database or not
Date: 2016-12-06 22:56:54
Message-ID: 0e7e2842-3544-e86d-75bf-d20952a13035@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/6/2016 1:02 PM, David Wall wrote:
> You can certainly put the files in a filesystem and point to them, but
> you'll likely need some access control or people will be able to
> download any/all PDFs in a given folder. In the DB, you surely will
> have access control as I presume you don't allow browser access to the
> DB <smile>.

thats easily remedied by using storage accessed via https or whatever
with directory listing disabled, and hashed names. Or, only allow your
app server direct access to the file system if its via NFS or whatever.

> Either way, you may want to see if your PDFs compress well or not as
> that may save some storage space at the cost of compress/decompress on
> accesses.

pretty sure most all PDF's are already compressed, and won't compress
much further.

--
john r pierce, recycling bits in santa cruz

In response to

Browse pgsql-general by date

  From Date Subject
Next Message DrakoRod 2016-12-07 01:58:16 FATAL: semctl(999999, 6, SETVAL, 0) failed: Invalid argument
Previous Message Joseph Brenner 2016-12-06 21:54:39 Re: Select works only when connected from login postgres