Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 21F269FB270 for ; Wed, 31 Jan 2007 18:12:55 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 02120-10 for ; Wed, 31 Jan 2007 18:12:48 -0400 (AST) X-Greylist: delayed 00:26:35.621111 by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 903069FB456 for ; Wed, 31 Jan 2007 18:12:51 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from server.firetrust.net (mailserver.firetrust.com [209.213.221.13]) by svr4.postgresql.org (Postfix) with ESMTP id D3D805AF8C6 for ; Wed, 31 Jan 2007 21:46:14 +0000 (GMT) Received: from localhost.localdomain (203-97-61-135.dsl.clear.net.nz [203.97.61.135]) by server.firetrust.net (8.13.8/8.13.8) with SMTP id l0VLk7Vj024627 for ; Thu, 1 Feb 2007 10:46:07 +1300 Date: Thu, 1 Feb 2007 10:46:06 +1300 From: Steve Holdoway To: pgsql-admin@postgresql.org Subject: blobs Message-Id: <20070201104606.5ea9e44e.steve.holdoway@firetrust.com> Organization: Firetrust Ltd X-Mailer: Sylpheed version 2.3.0beta5 (GTK+ 2.8.20; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV devel-20061113/2508/Thu Feb 1 05:42:50 2007 on server.firetrust.net X-Virus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.511 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO, SPF_FAIL X-Spam-Level: X-Archive-Number: 200701/304 X-Sequence-Number: 24460 I'm got the enviable task of redesigning an MySQL based project from scratch. We need a proper rdbms for this project, and I want to use PG 8.2. The table I'm concerned with at the moment have (currently) 5 million rows, with a churn of about 300,000 rows a week. The table has about a million hits a day, which makes it the main potential bottleneck in this database. We need to store some large ( 0 -> 100kB ) data with each row. Would you recommend adding it as columns in this table, given that blobs will be stored in the pg_largeobject table anyway, or would you recommend a daughter table for this? Any other suggestions on how to avoid performance problems with this table ( hardware is dual Xeon, 4GB mem, 2 hardware raid channels for storage + 1 for logs, all running debian 32 bit ). Cheers, Steve