Search Postgresql Archives

Re: Database versus filesystem for storing images

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On fös, 2007-01-05 at 15:49 -0500, Andrew Chernow wrote:
> I 100% agree.  Use the database as a lookup into the filesystem.  Don't load the 
> database up with terabytes of non-searchable binary data?  not sure how that 
> would help you?
> 

>  >I mean, how do you handle integrity with data
>  > outside the database?
> You don't, the file system handles integrity of the stored data.  Although, one 
> must careful to avoid db and fs orphans.  Meaning, a record with no 
> corresponding file or a file with no corresponging record.  Always 
> write()/insert an image file to the system within a transaction, including 
> writing the image out to the fs.  Make sure to unlink any paritally written 
> image files.

what happens if you rollback a transaction that just updated 
an image file?

for that matter, what happens if one transaction is using or
even reading an image while another is updating it?

gnari




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux