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 BAA57554 for ; Thu, 20 Apr 2000 01:45:54 -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 BAA01075; Thu, 20 Apr 2000 01:45:30 -0400 (EDT) To: Jan Wieck cc: Philippe Gobin , pgsql-sql@postgresql.org Subject: Re: TOAST (was: BLOB) In-reply-to: References: Comments: In-reply-to wieck@debis.com (Jan Wieck) message dated "Wed, 19 Apr 2000 19:12:11 +0200" Date: Thu, 20 Apr 2000 01:45:30 -0400 Message-ID: <1072.956209530@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200004/215 wieck@debis.com (Jan Wieck) writes: > To share some info with the other developers: > I just successfully stored the entire PG sources (~10M) in > one table. Stored are all 936 .[chyl] files. Cool! Sounds like you are making great progress. > Anyway, TOAST is on it's way. And as soon as we go for 7.1, > I'll need alot of help to make all our existing types > toastable, add administrative utility commands and teach > pg_dump to deal with all that. Question: pg_dump shouldn't need to know about toasted tuples as such, should it? I'm guessing that what you are thinking of is adding administration capabilities to control whether particular columns are toast-able, and then pg_dump would need to know about saving and loading those control fields. But toasting a particular field value ought to be invisible to applications... regards, tom lane