From: Josh Berkus <josh@agliodbs.com>
To: mallah@trade-india.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Storing text data in databases.
Date: Tue, 12 Feb 2002 08:22:54 -0800
Message-ID: <web-691666@davinci.ethosmedia.com> (raw)
In-Reply-To: <3C68AA95.38EE467C@trade-india.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, mallah@trade-india.com
Subject: Re: Storing text data in databases.
In-Reply-To: <web-691666@davinci.ethosmedia.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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