Re: TOAST and TEXT - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: TOAST and TEXT
Date
Msg-id 000901c1512d$3c2a7c40$8001a8c0@jester
Whole thread Raw
In response to TOAST and TEXT  (Chris Bitmead <chris@bitmead.com>)
Responses Re: TOAST and TEXT
List pgsql-hackers
It should be noted that there is still a limit of about 1GB if I
remember correctly.
--
Rod Taylor

There are always four sides to every story: your side, their side, the
truth, and what really happened.

----- Original Message -----
From: "Chris Bitmead" <chris@bitmead.com>
To: <pgsql-hackers@postgresql.org>
Sent: Tuesday, October 09, 2001 9:33 PM
Subject: [HACKERS] TOAST and TEXT


> Hi,
>
> Now that postgresql doesn't have field size limits, it seems to
> me they should be good for storing large blobs, even if it means
> having to uuencode them to be non-binary or whatever. I don't
> like the old large object implementation, I need to store very large
> numbers of objects and unless this implementation has changed
> in recent times it won't cut it.
>
> So my question is, I assume TEXT is the best data type to store
> large things in, what precisely is the range of characters that
> I can store in TEXT? Is it only characters ascii <= 127, or is
> it only printable characters, or everything except '\0' or what?
>
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>



pgsql-hackers by date:

Previous
From: Chris Bitmead
Date:
Subject: TOAST and TEXT
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: What about CREATE OR REPLACE FUNCTION?