| From: | Frank Joerdens <frank(at)joerdens(dot)de> |
|---|---|
| To: | Pam Withnall <Pamw(at)zoom(dot)com(dot)au> |
| Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TOAST |
| Date: | 2001-03-13 08:11:15 |
| Message-ID: | 20010313091115.A6501@rakete.joerdens.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 09, 2001 at 01:54:40PM +1100, Pam Withnall wrote:
> hi,
> I an using postgresql-7.1beta4 and am trying to use the large text fields.
> I have heard of TOAST. There is little documentation.
> I found one section about creating a data type,
> then creating two functions to convert the data types.
> Is this how TOAST is implemented?
> Am I on the right track?. If so, what do
> the conversion functions look like. I am using plpgsql.
> Thanks, Pam
TOAST works transparently for the user. It just means that the old
pre-7.1 8k (actually 32) row length limit is obsolete. In order to use
large text fields all you need to do is install 7.1 (which you already
have, as you say). No function creation etc. is required.
Regards, Frank
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2001-03-13 08:50:46 | Re: Do we still need PowerPC-specific timestamp_is_current/epoch? |
| Previous Message | Karel Zak | 2001-03-13 07:30:59 | Re: Internationalized error messages |