From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Barry Lind <barry(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Question about todo item |
Date: | 2001-08-05 02:35:59 |
Message-ID: | 200108050235.f752Zxj06918@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> By 'in/out interface for TOAST columns' I thought this item dealt with
> >> adding large object like functions to read/write/append to TOAST column
> >> data. I know that has been talked about in the past on hackers. But I
> >> don't see it on the todo list. Has that been done?
>
> > Only large objects allow that kind of access. I don't think we will do
> > that for TOAST columns.
>
> Barry's right --- that *has* been talked about, and I thought the
> consensus was that we needed such functions. You don't necessarily
> want to read or write a multi-megabyte TOASTed value all in one go.
> If it's not on TODO then it should be. (But I suspect if you check
> the archives, you'll discover that this is exactly what the TODO
> item was really about.)
Yes, I kept talking about it, but no one was interested, saying large
objects are better for that kind of access. When the uuencode idea came
around, I though the read/write binary toast idea was dead.
I agree we should have it, but I thought the problem was that we
couldn't come up with an API that worked.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-05 02:38:40 | Re: Question about todo item |
Previous Message | Tom Lane | 2001-08-05 02:33:17 | Re: Question about todo item |