From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Andrew Chernow <ac(at)esilo(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Extending varlena |
Date: | 2008-08-18 23:40:28 |
Message-ID: | 8329.1219102828@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Fetter <david(at)fetter(dot)org> writes:
> On Mon, Aug 18, 2008 at 06:09:13PM -0400, Andrew Chernow wrote:
>> I always find these requests puzzling. Is it really useful to store
>> the data for a jpeg, video file or a 10GB tar ball in a database
>> column?
> It is if you need transaction semantics. Think medical records, etc.
The basic problem with outside-the-DB data storage is keeping it in sync
with your inside-the-DB metadata. In a slowly changing dataset you can
probably get away with external storage, but if there's lots of updates
then allowing the DB to manage the storage definitely makes life easier.
This is not to say that you want SQL-style operations on the blobs;
in fact I think you probably don't, which is why I was pointing to
a LO-style API.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-08-19 00:18:40 | Re: pgbench duration option |
Previous Message | Tom Lane | 2008-08-18 23:31:04 | Re: Extending varlena |