Title: RE: [ADMIN] Tale partitioning
>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.
We just implemented partitioning, and have found it very useful for dropping old
l Message-
> From: Jim Nasby [mailto:[EMAIL PROTECTED]
> 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
> inp
Thanks...looks like partitioning will help.
-Original Message-
From: Jim Nasby [mailto:[EMAIL PROTECTED]
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
D]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jim C. Nasby
> Sent: Wednesday, April 26, 2006 3:51 PM
> To: Chris Hoover
> Cc: Benjamin Krajmalnik; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Tale partitioning
>
> On Wed, Apr 26, 2006 at 04:33:04PM -0400, Chris Hoover wrote:
> &
On Wed, Apr 26, 2006 at 04:33:04PM -0400, Chris Hoover wrote:
> Each of the partition tables needs it's own set of indexes. Build them, and
> see if the does not fix your performance issues. Also, be sure you turned
> on the constraint_exclusion parameter, and each table (other than the
> "master
Each of the partition tables needs it's own set of indexes. Build them, and see if the does not fix your performance issues. Also, be sure you turned on the constraint_exclusion parameter, and each table (other than the "master") has an constraint on it that is unique.
HTH,Chris
I have created a parent table and inherited into several
tables to facilitate table partitioning.
I noticed that the inherited tables did not inherit any of
the indices, etc. in their DDL.
Do these need to be created, or are they actually there via
inheritance but only “used” when the par
