From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Barry Lind <barry(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Question about todo item |
Date: | 2001-08-06 14:35:00 |
Message-ID: | 200108061435.f76EZ0207022@jupiter.us.greatbridge.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I agree we should have it, but I thought the problem was that we
> > couldn't come up with an API that worked.
>
> AFAIR, no one's really tried yet. I do not recall any proposals
> getting shot down ...
One of the problems I saw, and that's probably why we don't
have a proposal yet, is, that the size of the data is
recorded in the toast reference held in the main tuple. If
you later open the toast value for writing, you'll change the
size, but you'd need to change it in the main tuple too,
what'd require a regular update on the main tuple, what I
don't think we want to have here.
The other problem is, if you insert a tuple containing a
small value (e.g. empty string), it'll not get toasted and
you can't force it to get. Later you open it for writing and
pump a CD-image into. How do we convert the existing empty
text datum into a toast reference in the main tuple?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2001-08-06 14:40:18 | Re: Question about todo item |
Previous Message | Tom Lane | 2001-08-06 14:16:00 | Re: Possible solution for LIKE optimization |