<p>The main disadvantage that I often hear of using blobs is that, above a certain size, the file system is much more efficient at storing and retrieving large files.  It sounds like you've already taken this in to account by your list of requirements.</p>

<p>There's a <a href="http://arxiv.org/ftp/cs/papers/0701/0701168.pdf" rel="noreferrer">good reference (PDF) here</a> that covers the pros and cons of blobs.</p>
Storing Documents as Blobs in a Database - Any disadvantages?
<p>The requirements for my document management system were:</p>

<ol>
<li>Must be secure from theft by simple copying of directories, files etc.</li>
<li>Must be secure against traditional virus infection (infection of physical file)</li>
<li>Must be fast to retrieve</li>
<li>The repository must not be visible to casual (directory) browsing users etc.</li>
</ol>

<p>I have decided to store all documents (and scanned images) as blobs in the database and so far my experience is wonderful and document retrieval is blindingly fast as well - it meets all the criteria from above and there are even a couple of additional advantages, such as autostoring documents together with the entity it relates to, easy and fast seaching of contents, removing of all sorts of user activities around opening and naming of documents etc. etc.</p>

<p>My question is - are there any serious risks or things that I overlooked with this design and implementation?</p>

<p>EDIT Note: DB is PostgreSQL, handles BLOBS very well and scales exceptionally well. The environment is Multi-user.</p>