How do you deal with backing up the images? Right now i can remote
backup my filesystem using rsync to an offsite location many times a
day, only taking a very small amount of I/O, bandwidth and time.
Dealing with the backup scared me away from using postgres in the first
place. The idea of doing a 200gb dump multiple times a day on an
image database scares me. So does doing a vacuum on it. The I/O,
time and bandwidth required to do this is daunting.
Are there any suggestions on how to do incremental backups of the
images and any other suggestions on performance? In the future I'd
like to move some filesystem images to postgres to have a centralized
storage. It would make some things easier, but i'm not sure it's worth
the additional problems. Hopefully i'm imagining the problems.
--brian
On Tuesday, September 9, 2003, at 08:56 PM, Jonathan Bartlett wrote:
>> For the education of me and maybe others too, why was
>> that? i.e. what problems did you run into, that bytea avoids?
>>
>
> Compared to the filesystem, bytea provides data integrity.
>
> Bytea gives you remote access, which you can cache if needed.
>
> Bytea gives you the same permissions as anything else in Postgres, so
> you
> don't have to worry about that separately.
>
> Compared to BLOBs, bytea's are just simpler. You can select them with
> a
> single statement, you don't have to worry about leaving unreferenced
> BLOBs, and, after 4 billion inserts, byteas are still meaningful while
> BLOBs might not be. (due to OID problems).
>
> Jon
>
>
>> __________________________________
>> Do you Yahoo!?
>> Yahoo! SiteBuilder - Free, easy-to-use web site design software
>> http://sitebuilder.yahoo.com
>>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html