From: Jim C. Nasby <jnasby@pervasive.com>
To: Sriram Dandapani <sdandapani@counterpane.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Tale partitioning
Date: Thu, 4 May 2006 13:48:42 -0500
Message-ID: <20060504184841.GS97354@pervasive.com> (raw)
In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF041C362F@ca-mail1.cis.local>
References: <6992E470F12A444BB787B5C937B9D4DF041C362F@ca-mail1.cis.local>
BTW, I should have mentioned that partitioning is a very new feature and
that folks probably would like to know about shortcommings you find
while using it.
On Thu, May 04, 2006 at 11:40:51AM -0700, Sriram Dandapani wrote:
> Thanks...looks like partitioning will help.
>
> -----Original Message-----
> From: Jim Nasby [mailto:jnasby@pervasive.com]
> Sent: Thursday, May 04, 2006 11:37 AM
> To: Sriram Dandapani
> Cc: pgsql-admin@postgresql.org
> Subject: RE: [ADMIN] Tale partitioning
>
> Please include the mailing list in your replies so others can provide
> input.
>
> > From: Sriram Dandapani [mailto:sdandapani@counterpane.com]
> > Most of our reports use a order by limit X...The rowcount in
> > some tables
> > are > 200 million. (and the table size is about 50-100gb)
> >
> > Does the fact that constraint_exclusion doesn't deal with order by
> > /limit
> > makes partitioning an unwise choice.
>
> Well, in a worst-case scenario, partitioning will perform no worse than
> if you had one giant table. So it's not hurting you, it may just not be
> helping you.
>
> > What if the main query does just an order by and an outer query wraps
> > the inner query with a limit..
>
> It all depends on if the order-by code is partitioning aware, and I'm
> not sure that it is. But if you index on the appropriate column it
> should hopefully make use of that...
>
> > I am trying to figure out if I should use partitioning or not (my goal
> > is two-fold..purge lots of data in aged tables and make queries
> > partition-aware)
>
> Well, reason #1 sounds like plenty of justification for using
> partitioning to me.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
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-admin@postgresql.org
Cc: jnasby@pervasive.com, sdandapani@counterpane.com
Subject: Re: Tale partitioning
In-Reply-To: <20060504184841.GS97354@pervasive.com>
References: <6992E470F12A444BB787B5C937B9D4DF041C362F@ca-mail1.cis.local> <20060504184841.GS97354@pervasive.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