From: lars <lhofhansl@yahoo.com>
To: Samuel Gendler <sgendler@ideasculptor.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Statistics and Multi-Column indexes
Date: Fri, 15 Jul 2011 14:40:53 -0700
Message-ID: <4E20B3E5.6070507@yahoo.com> (raw)
In-Reply-To: <CAEV0TzDMkCXGDwPMm8nrK+cXL-fTCe56HvfJqe=BLtFOSfGbJQ@mail.gmail.com>
References: <4E1A1696.5010307@yahoo.com>
<CAEV0TzDMkCXGDwPMm8nrK+cXL-fTCe56HvfJqe=BLtFOSfGbJQ@mail.gmail.com>
On 07/10/2011 02:31 PM, Samuel Gendler wrote:
> What about partitioning tables by tenant id and then maintaining
> indexes on each partition independent of tenant id, since constraint
> exclusion should handle filtering by tenant id for you. That seems
> like a potentially more tolerable variant of #5 How many tenants are
> we talking about? I gather partitioning starts to become problematic
> when the number of partitions gets large.
>
I thought I had replied... Apparently I didn't.
The database can grow in two dimensions: The number of tenants and the
number of rows per tenant.
We have many tenants with relatively little data and a few with a lot of
data. So the number of tenants
is known ahead of time and might be 1000's.
-- Lars
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: lhofhansl@yahoo.com, sgendler@ideasculptor.com
Subject: Re: Statistics and Multi-Column indexes
In-Reply-To: <4E20B3E5.6070507@yahoo.com>
* 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