Re: Pre-creating partitions incurs insert penalty
От | Anj Adu |
---|---|
Тема | Re: Pre-creating partitions incurs insert penalty |
Дата | |
Msg-id | f2fd819a0905281743na5f4349va2b75ab914c7fdea@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Pre-creating partitions incurs insert penalty (Scott Marlowe <scott.marlowe@gmail.com>) |
Ответы |
Re: Pre-creating partitions incurs insert penalty
|
Список | pgsql-admin |
Partitioning is implemented via rules and check constraints to ensure partition integrity.
On Thu, May 28, 2009 at 5:21 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
On Thu, May 28, 2009 at 5:22 PM, Anj Adu <fotographs@gmail.com> wrote:How are you enforcing partiitoning on your inserts? Via app
> 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)
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.
В списке pgsql-admin по дате отправления: