pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mitch Vincent <mitch@venux.net>
To: svanegmond@home.com
Cc: pgsql-php@postgresql.org
Subject: Re: Question re large objects
Date: Tue, 28 Nov 2000 12:54:39 -0800
Message-ID: <014101c0597d$6d38ffd0$0200000a@windows> (raw)
References: <3A23B26E.9056.2942B3@localhost>
	<20001128132923.B30495@bang.dhs.org>
	<011201c05976$c76df8e0$0200000a@windows>
	<20001128143410.A30737@bang.dhs.org>

> BLOBs are not dumped from pgsql.

OK, that makes sense -- I do a file system backup though, in addition to
pg_dump..

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

You're right, I didn't understand large objects (never had any reason to use
them), I thought PG implemented BLOBs as a data type like *gulp* MySQL
*gulp*. I shouldn't have opened my mouth until I educated myself on them...

It seems that large objects are quite useless if you can't dump the data
(since as you point out, it's not SQL) though I guess a filesystem backup
would still work.. They sound like a disaster waiting to happen, glad I
haven't needed them...

An additional note (now that I read about Large Objects) it seems they're
broken up into different tuples so I guess they're total size isn't limited
by the BLCKSZ eh'?

Oh well, I still like flat-file storage for Christopher's project, even more
so now...

Thanks for pointing out my ignorance on this subject, I learned something.


-Mitch





view thread (16+ messages)  latest in thread

Message-ID: <014101c0597d$6d38ffd0$0200000a@windows>
Permalink:  ../014101c0597d$6d38ffd0$0200000a@windows/
Also on:    postgresql.org/message-id/014101c0597d$6d38ffd0$0200000a@windows

 · 

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