| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Radosław Smogura <rsmogura(at)softperience(dot)eu> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BLOB support |
| Date: | 2011-06-02 12:39:39 |
| Message-ID: | 1307018379.2279.14.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On ons, 2011-06-01 at 22:00 +0200, Radosław Smogura wrote:
> I partialy implemented following missing LOBs types. Requirement for this was
> to give ability to create (B/C)LOB columns and add casting functionality e.g.
> SET my_clob = 'My long text'.
>
> Idea is as follow:
> 0. Blob is two state object: 1st in memory contains just bytea, serialized
> contains Oid of large object.
> 1. Each type has additional boolean haslobs, which is set recursivly.
> 2. Relation has same bool haslobs (used to speed up tables without LOBs)
> 3. When data are inserted/updated then "special" function is called and tuple
> is modified in this way all LOBs are serialized to (old) LOB table and just
> Oid is stored.
> 4. When removed LOB is removed from (old) LOB table.
Superficially, this looks like a reimplementation of TOAST. What
functionality exactly do you envision that the BLOB and CLOB types would
need to have that would warrant treating them different from, say, bytea
and text?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2011-06-02 12:58:52 | Re: BLOB support |
| Previous Message | Andrew Dunstan | 2011-06-02 12:16:31 | Re: Hacking gram.y Error syntax error at or near "MERGEJOIN" |