From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jan Wieck <wieck@debis.com>
Cc: Philippe Gobin <philippe.gobin@fth.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: TOAST (was: BLOB)
Date: Thu, 20 Apr 2000 01:45:30 -0400
Message-ID: <1072.956209530@sss.pgh.pa.us> (raw)
In-Reply-To: <m12hy1L-0003knC@orion.SAPserv.Hamburg.dsh.de>
References: <m12hy1L-0003knC@orion.SAPserv.Hamburg.dsh.de>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, wieck@debis.com, philippe.gobin@fth.net
Subject: Re: TOAST (was: BLOB)
In-Reply-To: <1072.956209530@sss.pgh.pa.us>
References: <m12hy1L-0003knC@orion.SAPserv.Hamburg.dsh.de> <1072.956209530@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox