Re: tuptoaster.c must *not* use SnapshotAny

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Jan Wieck <janwieck(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: tuptoaster.c must *not* use SnapshotAny
Date: 2002-01-18 05:27:50
Message-ID: 4476.1011331670@sss.pgh.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:
> Well, we had the discussion when Jan was adding TOAST, and Jan was
> saying we still need large objects for I/O purposes and for very large
> items.

Yeah. I hadn't realized until this conversation that TOAST couldn't
support partial updates of huge values. That is a definite problem for
supporting lo_read/lo_write-type operations.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2002-01-18 05:38:57 Re: age() function?
Previous Message Bruce Momjian 2002-01-18 05:27:10 Re: tuptoaster.c must *not* use SnapshotAny