Re: Question re large objects

From: "Mitch Vincent" <mitch(at)venux(dot)net>
To: <svanegmond(at)home(dot)com>
Cc: <pgsql-php(at)postgresql(dot)org>
Subject: Re: Question re large objects
Date: 2000-11-28 20:54:39
Message-ID: 014101c0597d$6d38ffd0$0200000a@windows
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-php

> 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

In response to

Browse pgsql-php by date

  From Date Subject
Next Message Chris 2000-11-28 22:02:54 RE: Question re large objects
Previous Message Mitch Vincent 2000-11-28 20:07:04 Re: Question re large objects