Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA33360 for ; Fri, 21 Apr 2000 17:59:56 -0400 (EDT) (envelope-from peter@localhost.its.uu.se) Received: from regulus.student.UU.SE ([130.238.5.2]:38486 "EHLO regulus.its.uu.se") by merganser.its.uu.se with ESMTP id ; Fri, 21 Apr 2000 23:59:49 +0200 Received: from peter (helo=localhost) by regulus.its.uu.se with local-esmtp (Exim 3.02 #2) id 12ilWr-0000bA-00; Sat, 22 Apr 2000 00:04:01 +0200 Date: Sat, 22 Apr 2000 00:04:01 +0200 (CEST) From: Peter Eisentraut To: Jan Wieck cc: pgsql-sql@postgresql.org Subject: Re: TOAST (was: BLOB) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Archive-Number: 200004/244 Jan Wieck writes: > I just successfully stored the entire PG sources (~10M) in > one table. Stored are all 936 .[chyl] files. Cool, then we can get rid of CVS. :-) > clob is a user defined, very simple varsize datatype, I > created for testing. Keep it, it's SQL3. > Seems there's something wrong in our deadlock detection > algorithm. Our deadlock detection "algorithm" is that when nothing happens for 1 sec then that's a deadlock. Increasing that number might make those messages go away but that's still far from an algorithm, of course. > I'll need alot of help to make all our existing types > toastable, I'm wondering how transparent all of this will be. What is involved in making existing types toastable? How does that affect user defined datatypes now and in the future? -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden