From: Mitch Vincent <mitch@venux.net>
To: svanegmond@home.com
To: chriswood@wvda.com
Cc: pgsql-php@postgresql.org
Subject: Re: Question re large objects
Date: Tue, 28 Nov 2000 12:07:04 -0800
Message-ID: <011201c05976$c76df8e0$0200000a@windows> (raw)
References: <3A23B26E.9056.2942B3@localhost>
<20001128132923.B30495@bang.dhs.org>
> Because you will lose the images when you do a restore from backup.
> And you will have to restore from backup eventually, count on it.
I think one should always plan for the worst case scenerio, that's exactly
thye you do backups, so you don't lose data.. Why would he lose data if he's
preforming backups and restored from that backup..
Unless the backup wasn't preformed or failed in some way, he wouldn't lose
any data..
> On the other hand, if your service will ever grow to more than one
> computer doing HTTP service (i.e. load balancing), you will have to
> have the items in the database or resort to unsightly things like NFS.
Again, I always think one should make an application scaleable but having
said that, I think what you're mentioning here is a cart before the horse
situation. Even saying he needed to load balance I'd never use NFS, ever.
Large RAID arrays and such could provide all the storage needed --
especially since we're just talking about images here.
> If you expect your site to get big or be busy, you will have to come up
> with a way (preferably an abstraction on top of pg_lo* functions) that
> will preserve the BLOBs in the database so that when you do a reload,
> you can pump in the BLOBs as well and connect their *new* OIDs with the
> appropriate table. Because the OIDs will change when you reload.
>
> You do have a backup plan, right?
I'd suggest that you don't use OIDs as binding record IDs, make another
integer field for that. There is an option to pg_dump to preserve OIDs even
if you do.
-Mitch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: mitch@venux.net, svanegmond@home.com, chriswood@wvda.com
Subject: Re: Question re large objects
In-Reply-To: <011201c05976$c76df8e0$0200000a@windows>
References: <3A23B26E.9056.2942B3@localhost> <20001128132923.B30495@bang.dhs.org> <011201c05976$c76df8e0$0200000a@windows>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox