From: | "Richard Huxton" <dev(at)archonet(dot)com> |
---|---|
To: | <pgsql-general(at)commandprompt(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Doug McNaught" <doug(at)wireboard(dot)com>, "Michael" <mwaples(at)waples(dot)net>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Databases compared at zend.com |
Date: | 2001-06-02 22:32:32 |
Message-ID: | 006801c0ebb4$a6ffda80$1001a8c0@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> > could someone please describe the actual process,
>
> Large objects are now stored in pg_largeobject. Each LO is broken into
> chunks of a couple K apiece, and each chunk becomes a row. (Chunking
> makes partial updates more efficient, since you don't have to rewrite
> the entire LO.) The LO operations aren't really special, they're just a
> convenient interface for insert/update/delete operations in this table.
>
> Before 7.1, it worked the same except that each LO had its own table.
Perhaps a clear note in the docs - I definitely had the (mis-)impression
that LO's were standard files referenced by PG. That could have been my
background though, since that's how I tend to deal with documents/images
anyway.
- Richard Huxton
From | Date | Subject | |
---|---|---|---|
Next Message | pipothebit | 2001-06-02 23:20:17 | add java as procedural language |
Previous Message | Tom Janssens | 2001-06-02 20:47:20 | QUESTION: Automatically generating Primary keys !!! |