| From: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Inserting heap tuples in bulk in COPY |
| Date: | 2011-08-12 19:44:47 |
| Message-ID: | CABwTF4X1+aN4=RVBmHPgrvG_TVeQysrVyz49qKbAPVkJnJ1WFA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 12, 2011 at 3:16 PM, Heikki Linnakangas <
heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> COPY is slow.
No kidding!
> So at least for now, the patch simply falls back to inserting one row at a
> time if there are any triggers on the table.
>
Maybe we want to change that to "fall back to old ways if there are any FOR
EACH ROW triggers", since FOR EACH STATEMENT triggers won't be bothered by
this optimization.
--
Gurjeet Singh
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2011-08-12 19:57:11 | Re: Inserting heap tuples in bulk in COPY |
| Previous Message | Tom Lane | 2011-08-12 19:41:41 | Re: VACUUM FULL versus system catalog cache invalidation |