| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-general(at)commandprompt(dot)com |
| 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-01 18:48:58 |
| Message-ID: | 6172.991421338@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> As the person who wrote it :) It was my understanding that PostgreSQL
> stores large objects on the filesystem outside of the database tables.
Definitely not true.
I think that was once an available option, many years ago ... but
it's not there now.
> 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-06-01 18:51:11 | Re: Can't restart postmaster! |
| Previous Message | Doug McNaught | 2001-06-01 18:34:50 | Re: Databases compared at zend.com |