From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Radosław Smogura <rsmogura(at)softperience(dot)eu>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: BLOB support |
Date: | 2011-06-03 14:44:13 |
Message-ID: | 26724.1307112253@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Radosaw Smogura's message of jue jun 02 15:26:29 -0400 2011:
>> So do I understand good should We think about create bettered TOAST to support
>> larger values then 30-bit length? I like this much more,
> Good :-)
> (BTW while it'd be good to have longer-than-30 bit length words for
> varlena, I'm not sure we have room for that.)
You wouldn't want to push such values around as whole values anyway.
Possibly what would work here is a variant form of TOAST pointer for
which we'd simply throw error if you tried to fetch the entire value
at once.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alexey Klyukin | 2011-06-03 15:11:37 | Re: Identifying no-op length coercions |
Previous Message | Tom Lane | 2011-06-03 14:42:01 | Re: Domains versus polymorphic functions, redux |