From: | Ian Westmacott <ianw(at)intellivid(dot)com> |
---|---|
To: | blblack(at)gmail(dot)com |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Performance considerations for very heavy INSERT |
Date: | 2005-09-13 16:16:55 |
Message-ID: | 1126628214.11675.55.camel@spectre.intellivid.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, 2005-09-13 at 11:30, Brandon Black wrote:
> I started looking closer at my options for partitioning (inheritance,
> union all), and at Bizgres today. Bizgres partitioning appears to be
> basically the same kind of inheritance partitioning one can do in
> mainline PostgreSQL. Am I correct in thinking that the main
> difference is that they've coded support for
> "enable_constraint_exclusion=true" so that the query planner can be
> more effective at taking advantage of the partitioning when you've
> specified CHECK constraints on the child tables? I may go for 8.1
> instead in that case, as the main win I'm looking for is that with
> inheritance I'll be doing inserts into smaller tables instead of ones
> that grow to unmanageable sizes (and that I can drop old child tables
> instead of delete/vacuum).
Perhaps I missed something in this thread, but don't forget
you still need vacuum to reclaim XIDs.
--Ian
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-09-13 17:22:43 | Re: Performance considerations for very heavy INSERT |
Previous Message | Tom Lane | 2005-09-13 15:32:02 | Re: Low performance on Windows problem |