X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 09E364761F6 for ; Fri, 31 Jan 2003 01:28:42 -0500 (EST) Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by postgresql.org (Postfix) with ESMTP id 3E50D475C2B for ; Fri, 31 Jan 2003 01:28:37 -0500 (EST) Received: (from root@localhost) by www.pspl.co.in (8.11.6/8.11.6) id h0V6RHK27150 for ; Fri, 31 Jan 2003 11:57:17 +0530 Received: from daithan.intranet.pspl.co.in (daithan.intranet.pspl.co.in [192.168.7.161]) by www.pspl.co.in (8.11.6/8.11.0) with ESMTP id h0V6RH527145 for ; Fri, 31 Jan 2003 11:57:17 +0530 Content-Type: text/plain; charset="iso-8859-1" From: "Shridhar Daithankar" To: pgsql-performance@postgresql.org Subject: Re: One large v. many small Date: Fri, 31 Jan 2003 11:57:40 +0530 User-Agent: KMail/1.4.3 References: <176C96F6-3480-11D7-A3A3-000393AA8F3C@allresearch.com> In-Reply-To: <176C96F6-3480-11D7-A3A3-000393AA8F3C@allresearch.com> MIME-Version: 1.0 Message-Id: <200301311157.40351.shridhar_daithankar@persistent.co.in> X-MIME-Autoconverted: from quoted-printable to 8bit by www.pspl.co.in id h0V6RH527145 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/400 X-Sequence-Number: 1047 On Thursday 30 Jan 2003 11:54 pm, you wrote: > As I mentioned in our earlier post, we are attempting to decide if > Postgres will run faster/better/ with one big table, or a bunch of > smaller ones. It really doesn't make much difference to us, we just > want whatever structure will be faster. I would say create a big table with client id. Create a index on it and cre= ate=20 3000 views. Of course you need to figure out SQL voodoo to insert into=20 postgresql views using rules. But that would save you from modifying your app. up and down. But there is= =20 going to be massive framgmentation. Consider clustering tables once in a=20 while. HTH Shridhar