> Well just having them in the database won't affect performance directly. > > But there are indirect effects: > > 1) If you're accessing them regularly then the disk data will be cached by the > kernel just like other tables, and will contend with the much denser data > from your data tables. > > 2) Backups and restores will have to slog through that data as well and take > correspondingly longer. Right. One thing to consider is whether your files will change often or be mostly static. I store them in the file system because the files I'm dealing with right now never get updated. If they were in the database then my simple database backup (pg_dumpall) would copy them all every time. By keeping them in the file system it's easy to use utilities which do incremental backup, and thus only new files need be copied. -- Scott Ribe scott_ribe@killerbytes.com http://www.killerbytes.com/ (303) 665-7007 voice ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
