Re: Inserting heap tuples in bulk in COPY - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: Inserting heap tuples in bulk in COPY
Date
Msg-id CABwTF4X1+aN4=RVBmHPgrvG_TVeQysrVyz49qKbAPVkJnJ1WFA@mail.gmail.com
Whole thread Raw
In response to Inserting heap tuples in bulk in COPY  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Fri, Aug 12, 2011 at 3:16 PM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: VACUUM FULL versus system catalog cache invalidation
Next
From: Florian Pflug
Date:
Subject: Re: Inserting heap tuples in bulk in COPY