| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Draft release notes complete |
| Date: | 2012-05-22 21:27:47 |
| Message-ID: | 20120522212747.GC10306@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 16, 2012 at 10:49:25PM +0300, Heikki Linnakangas wrote:
> On 16.05.2012 22:38, Jeff Janes wrote:
> >For item:
> >Improve COPY performance by adding tuples to the heap in batches
> >(Heikki Linnakangas)
> >
> >I think we should point out that the batching only applies for COPY
> >into unindexed tables. Nice as the feature is, that is pretty big
> >limitation not to mention.
>
> No, it applies to indexed tables too. However, if there are indexes
> on the table, the overhead of updating the indexes will probably
> make any speedup in the heap insertions look tiny in comparison.
>
> The optimization doesn't apply if the table has BEFORE or INSTEAD OF
> triggers, or volatile DEFAULT expressions need to be evaluated.
So, I will assume the existing wording is fine.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-05-22 21:36:38 | Re: Add primary key/unique constraint using prefix columns of an index |
| Previous Message | Bruce Momjian | 2012-05-22 21:26:45 | Re: Draft release notes complete |