Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA61560 for ; Sat, 22 Apr 2000 13:12:41 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id NAA26928; Sat, 22 Apr 2000 13:12:36 -0400 (EDT) To: Jan Wieck cc: Peter Eisentraut , pgsql-sql@postgresql.org Subject: Re: TOAST (was: BLOB) In-reply-to: References: Comments: In-reply-to wieck@debis.com (Jan Wieck) message dated "Sat, 22 Apr 2000 10:52:03 +0200" Date: Sat, 22 Apr 2000 13:12:36 -0400 Message-ID: <26925.956423556@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200004/254 wieck@debis.com (Jan Wieck) writes: >> Net result for user-defined-datatype authors will be "if you revise >> your routines, they will be easier to read, more portable, and will >> support TOASTed values. If you don't, they'll still work about as >> well (or poorly) as they did before." > Sorry, but that ain't true. Making an existing type toastable > means that all functions, receiving that type need to be > revised. What I meant was that they'd still work, with a limit on field size, just like before. ie, no TOAST support. regards, tom lane