| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Draft release notes complete |
| Date: | 2012-05-16 19:49:25 |
| Message-ID: | 4FB404C5.4030401@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2012-05-16 20:53:51 | Re: Pre-alloc ListCell's optimization |
| Previous Message | Jeff Janes | 2012-05-16 19:38:15 | Re: Draft release notes complete |