From: "Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
From: " <shridhar_daithankar@persistent.co.in>
To: pgsql-performance@postgresql.org
Subject: Re: One large v. many small
Date: Fri, 31 Jan 2003 11:57:40 +0530
Message-ID: <200301311157.40351.shridhar_daithankar@persistent.co.in> (raw)
In-Reply-To: <176C96F6-3480-11D7-A3A3-000393AA8F3C@allresearch.com>
References: <176C96F6-3480-11D7-A3A3-000393AA8F3C@allresearch.com>
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 create
3000 views. Of course you need to figure out SQL voodoo to insert into
postgresql views using rules.
But that would save you from modifying your app. up and down. But there is
going to be massive framgmentation. Consider clustering tables once in a
while.
HTH
Shridhar
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: shridhar_daithankar@persistent.co.in
Subject: Re: One large v. many small
In-Reply-To: <200301311157.40351.shridhar_daithankar@persistent.co.in>
References: <176C96F6-3480-11D7-A3A3-000393AA8F3C@allresearch.com> <200301311157.40351.shridhar_daithankar@persistent.co.in>
* 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