pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen van Egmond <svanegmond@bang.dhs.org>
To: Mitch Vincent <mitch@venux.net>
Cc: svanegmond@home.com
Cc: chriswood@wvda.com
Cc: pgsql-php@postgresql.org
Subject: Re: Question re large objects
Date: Tue, 28 Nov 2000 14:34:10 -0500
Message-ID: <20001128143410.A30737@bang.dhs.org> (raw)
In-Reply-To: <011201c05976$c76df8e0$0200000a@windows>
References: <3A23B26E.9056.2942B3@localhost>
	<20001128132923.B30495@bang.dhs.org>
	<011201c05976$c76df8e0$0200000a@windows>

Mitch Vincent (mitch@venux.net) wrote:

> > 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..

BLOBs are not dumped from pgsql.

This might be because there's no valid SQL to create BLOBs, and since
pgsql dumps are supposed to be SQL, it just doesn't work.

> 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.

I'm referring to multiple serving machines due to CPU or local disk 
capacity.

> 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.

I don't think you understand large objects.  When you create one, you
get an OID. When you want to retrieve it, you hand it the OID.  
End of story.  And, again, they are dumped by pg_dump.



view thread (16+ messages)  latest in thread

Message-ID: <20001128143410.A30737@bang.dhs.org>
Permalink:  ../20001128143410.A30737@bang.dhs.org/
Also on:    postgresql.org/message-id/20001128143410.A30737@bang.dhs.org

 · 

reply

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: svanegmond@bang.dhs.org, mitch@venux.net, svanegmond@home.com, chriswood@wvda.com
  Subject: Re: Question re large objects
  In-Reply-To: <20001128143410.A30737@bang.dhs.org>
  References: <3A23B26E.9056.2942B3@localhost> <20001128132923.B30495@bang.dhs.org> <011201c05976$c76df8e0$0200000a@windows> <20001128143410.A30737@bang.dhs.org>

* 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