pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedStoring text data in databases.
3+ messages / 3 participants
[nested] [flat]
* Storing text data in databases.
@ 2002-02-12 05:39 mallah@trade-india.com
0 siblings, 2 replies; 3+ messages in thread
From: mallah@trade-india.com @ 2002-02-12 05:39 UTC (permalink / raw)
To: pgsql-sql
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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Storing text data in databases.
@ 2002-02-12 06:04 Christopher Kings-Lynne <chriskl@familyhealth.com.au>
parent: mallah@trade-india.com
1 sibling, 0 replies; 3+ messages in thread
From: Christopher Kings-Lynne @ 2002-02-12 06:04 UTC (permalink / raw)
To: mallah@trade-india.com; 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@postgresql.org
> [mailto:pgsql-sql-owner@postgresql.org]On Behalf Of
> mallah@trade-india.com
> Sent: Tuesday, 12 February 2002 1:40 PM
> To: pgsql-sql@postgresql.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@postgresql.org so that your
> message can get through to the mailing list cleanly
>
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Storing text data in databases.
@ 2002-02-12 16:22 Josh Berkus <josh@agliodbs.com>
parent: mallah@trade-india.com
1 sibling, 0 replies; 3+ messages in thread
From: Josh Berkus @ 2002-02-12 16:22 UTC (permalink / raw)
To: mallah@trade-india.com; +Cc: pgsql-sql
Mallah,
> 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.
Thanks to the team's work on TOAST, performance is about equal. The
real question for you to answer is what better suits your data? If
you are using the database for version control, or to serve web pages,
then I would say definitely in the table. However, if this is a
document tracking database just designed to help you find papers, then
I would say use linked files.
If you store the data in the database, you may have to pay close
attention to your disk allocation. If this database sees heavy use,
you may even need to move just that table to a seperate disk to
prevent disk-access slowdowns. Of course, if you are using RAID-5,
this is not an issue.
-Josh Berus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2002-02-12 16:22 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-02-12 05:39 Storing text data in databases. mallah@trade-india.com
2002-02-12 06:04 ` Christopher Kings-Lynne <chriskl@familyhealth.com.au>
2002-02-12 16:22 ` Josh Berkus <josh@agliodbs.com>
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