Re: Large Objects

One obvious solution is to handle this at the application level. Read database
to get path to image file, retrieve image file if it exists, and if it doesn't
exist, delete or modify the database record to reflect what you just learned
about reality. If necessary, you could periodically go through every path in the
database to verify their existence on the FS, and delete the path records for
missing files en masse, though I wouldn't do this too often.

Hope this helps,

Wes

Nadim Bitar <nadiizu%earthlink(dot)net(at)interlock(dot)lexmark(dot)com> on 06/27/2002 06:10:07
AM

To: Karel Zak <zakkr%zf(dot)jcu(dot)cz(at)interlock(dot)lexmark(dot)com>
cc: pgsql-general%postgresql(dot)org(at)interlock(dot)lexmark(dot)com (bcc: Wesley
Sheldahl/Lex/Lexmark)
Subject: Re: [GENERAL] Large Objects

The only thing that concerns me about using the filesystem is what
happens if the user deletes an image from the FS, the image table would
be in an inconsistent state. Still trying to think of an elegant
solution to solve that.

On