Hello Emi Lu,
The detailed discussion was just about two weeks ago on the plpgsql
list, worth of glance.
Actually it is quite difficult to say which one is better in your case
as it depends on utility (rapid file hostin or just storing but
transaction safety is important, etc.).
Generally it seems that your requirements are rather small.
So briefly, my point of view on it:
(1) Pro:
- easy to implement,
- more efficient when storing and retrieving files than other solutions
- easy hosting over dedicated file server (with caching i.e.)
- DB size is small, files are separated - important on shared hosting
where DB size limit is usually much smaller than file storage limit.
Cons:
- nontransactional - actually you may try to create double commit but it
still may fail as it is not "atomic" operation, on two (FS and DB)
- more complicated to backup and restore.
(2) no opinion on mine
(3)
Pro:
- consistent,
- smart solution ;-)
- easy to backup / restore
- transactional
Cons:
- harder to implement storing and retrieving files
- may be non efficient (usually requires app side caching)
- DB size is bigger
Regards,
P.
--
--------------------------------------------------------------
"TECHBAZA.PL" Sp. z o.o.
Technologie WEB, eDB& eCommerce
tel. (+4832) 7186081
fax. (+4832) 7003289
email: bi...@techbaza.pl
web: http://www.techbaza.pl
web: partner.techbaza.pl
web: ekspert.techbaza.pl
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
