Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g1CGMpE90978 for ; Tue, 12 Feb 2002 11:22:51 -0500 (EST) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 691666; Tue, 12 Feb 2002 08:22:54 -0800 From: "Josh Berkus" Subject: Re: Storing text data in databases. To: mallah@trade-india.com Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Tue, 12 Feb 2002 08:22:54 -0800 Message-ID: In-Reply-To: <3C68AA95.38EE467C@trade-india.com> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200202/133 X-Sequence-Number: 6561 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