From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Lee Russell <lee(at)zoom(dot)com(dot)au> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Large Text Fields and TOAST |
Date: | 2001-03-13 02:33:19 |
Message-ID: | Pine.BSF.4.21.0103121831320.98920-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Well, TOAST should be fairly transparent to users I believe. TOAST
values should be compressed or stored separately from the rest of
the row's data to get around the 8-32k block size.
There's also the large object support which is something else entirely.
On Fri, 9 Mar 2001, Lee Russell 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Arnold | 2001-03-13 02:34:43 | Re: pqReadData() - backend unexpectedly closed the channel |
Previous Message | Stephan Szabo | 2001-03-13 02:30:55 | Re: Create trigger problem : |