X-Original-To: pgsql-performance@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 55C264758C9 for ; Sun, 27 Apr 2003 22:30:23 -0400 (EDT) Received: from cable.kevindegraaf.net (12-245-24-71.client.attbi.com [12.245.24.71]) by postgresql.org (Postfix) with SMTP id 9B638474E42 for ; Sun, 27 Apr 2003 22:30:20 -0400 (EDT) Received: (qmail 1371 invoked from network); 28 Apr 2003 02:30:31 -0000 Received: from unknown (HELO ungoliant) (192.168.1.3) by cable.kevindegraaf.net with SMTP; 28 Apr 2003 02:30:31 -0000 From: Jeremy Andrus Reply-To: jeremy@jeremya.com Organization: http://www.jeremya.com/ To: pgsql-performance@postgresql.org Subject: pgsql BLOB issues Date: Sun, 27 Apr 2003 22:30:23 -0400 User-Agent: KMail/1.5 X-Rokken: Dokken MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304272230.23583@jeremy-rokks> X-Spam-Status: No, hits=-5.8 required=5.0 tests=BAYES_10,USER_AGENT version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/221 X-Sequence-Number: 1727 Hello, I have a database that contains a large amount of Large Objects (>500MB). I am using this database to store images for an e-commerce website, so I have a simple accessor script written in perl to dump out a blob based on a virtual 'path' stored in a table (and associated with the large object's OID). This system seemed to work wonderfully until I put more than ~500MB of binary data into the database. Now, every time I run the accessor script (via the web OR the command line), the postmaster process gobbles up my CPU resources (usually >30% for a single process - and it's a 1GHz processor with 1GB of RAM!), and the script takes a very long time to completely dump out the data. I have the same issue with an import script that reads files from the hard drive and puts them into Large Objects in the database. It takes a very long time to import whereas before, it would run extremely fast. Are there any known issues in PostgreSQL involving databases with a lot of binary data? I am using PostgreSQL v7.2.3 on a linux system. Thanks, -Jeremy -- ------------------------ Jeremy C. Andrus http://www.jeremya.com/ ------------------------