Received: from smtp1b.mail.yahoo.com (smtp3.mail.yahoo.com [128.11.68.135]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f0TI5hq17506 for ; Mon, 29 Jan 2001 13:05:43 -0500 (EST) (envelope-from janwieck@yahoo.com) Received: from j13.us.greatbridge.com (HELO jupiter.greatbridge.com) (216.54.52.153) by smtp.mail.vip.suc.yahoo.com with SMTP; 29 Jan 2001 19:05:07 -0000 X-Apparently-From: Received: (from janwieck@localhost) by jupiter.greatbridge.com (8.9.3/8.9.3) id NAA03883; Mon, 29 Jan 2001 13:10:37 -0500 From: Jan Wieck Message-Id: <200101291810.NAA03883@jupiter.greatbridge.com> Subject: Re: BLOB HOWTO?? In-Reply-To: <200101291637.LAA15424@candle.pha.pa.us> from Bruce Momjian at "Jan 29, 2001 11:37:19 am" To: Bruce Momjian Date: Mon, 29 Jan 2001 13:10:37 -0500 (EST) CC: ohp@pyrenet.fr, pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/1312 X-Sequence-Number: 4077 Bruce Momjian wrote: > > Hi Bruce, > > > > Any idea when it's due for?? > > When? Probably not until 7.2, which is a pain. We cannot use TOAST as is for BLOB/CLOB storage with a binary IO interface over fastpath. The reason is that you cannot force a column to be moved off anyway and that the toast reference contains the original objects size. Thus, opening a BLOB for writing would require the reference in the main tuple to get updated and maybe moving off the data first. My plans for 7.2 are to use the toast table for storage, but to build new data types with support hooks in the toaster for it. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com # _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com