| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Chris Hoover <revoohc(at)gmail(dot)com> |
| Cc: | Benjamin Krajmalnik <kraj(at)illumen(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Tale partitioning |
| Date: | 2006-04-26 22:50:36 |
| Message-ID: | 20060426225036.GG97354@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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") has an constraint on it that is unique.
I don't believe constraint_exclusion is smart enough to deal with ORDER
BY / LIMIT yet... :/
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-04-26 22:52:01 | Re: Table partitioning |
| Previous Message | Jim C. Nasby | 2006-04-26 22:47:32 | Re: dbsize & pg_dump |