From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | <mallah(at)trade-india(dot)com>, <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Storing text data in databases. |
Date: | 2002-02-12 06:04:49 |
Message-ID: | GNELIHDDFBOCMGBFGEFOEEFKCBAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi Mallah,
Postgres 7.1 and above store large text fields (as type 'text') efficiently.
Just use Postgres and don't worry about it! In fact, postgres itself stores
the large data in a separate table for just the performance reasons you
give! However this is totally transparent to you, the user.
You can use the 'bytea' type for binary data of any size.
Chris
> -----Original Message-----
> From: pgsql-sql-owner(at)postgresql(dot)org
> [mailto:pgsql-sql-owner(at)postgresql(dot)org]On Behalf Of
> mallah(at)trade-india(dot)com
> Sent: Tuesday, 12 February 2002 1:40 PM
> To: pgsql-sql(at)postgresql(dot)org
> Subject: [SQL] Storing text data in databases.
>
>
> Hi folks,
> Is it a good idea to store large amount of text ( ~ 5-10 K ) in
> database
> columns from performance point of view? or store the text in sperate
> files and store the id of the file in the databases.
>
> Mallah.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2002-02-12 06:21:42 | Re: Sequencing Problem in Transaction.. |
Previous Message | Christopher Kings-Lynne | 2002-02-12 06:02:22 | Re: Sequencing Problem in Transaction.. |