From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Anj Adu <fotographs(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Pre-creating partitions incurs insert penalty |
Date: | 2009-05-29 00:21:13 |
Message-ID: | dcc563d10905281721x7890139er5e84b0e980e5bc31@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, May 28, 2009 at 5:22 PM, Anj Adu <fotographs(at)gmail(dot)com> wrote:
> I noticed a very strange performance issue after I pre-create daily
> partitions for the next month on a table that has a very large insert volume
> (30 million a day). After the partitions are created..the inserts seem to
> slow down. I verifiied that this was the issue by dropping the
> partitions...When I dropped the pre-created partitions..the performance
> issue disappeared. Looks like you cannot have too many partitions (in this
> case..I had a total of 35 partitions when the performance issue was noticed)
How are you enforcing partiitoning on your inserts? Via app
knowledge, triggers, or rules? I'd expect rules might have a penalty
with more partitions, but not expect it from app or trigger based
partitioning.
From | Date | Subject | |
---|---|---|---|
Next Message | Anj Adu | 2009-05-29 00:43:20 | Re: Pre-creating partitions incurs insert penalty |
Previous Message | Kevin Grittner | 2009-05-29 00:18:20 | Re: Continuous archiving fails routinely with "invalid magic number" error |