Horton

Re: Seq scans roadmap

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "CK Tan" <cktan@greenplum.com>
Cc: "Luke Lonergan" <llonergan@greenplum.com>, "Simon Riggs" <simon@enterprisedb.com>, "Heikki Linnakangas" <heikki@enterprisedb.com>, "PostgreSQL-development" <pgsql-hackers@postgresql.org>, "Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>, "Jeff Davis" <pgsql@j-davis.com>
Date: 2007-05-13T23:54:24Z
Lists: pgsql-hackers 
"CK Tan" <cktan@greenplum.com> writes:
> COPY/INSERT are also bottlenecked on record at a time insertion into  
> heap, and in checking for pre-insert trigger, post-insert trigger and  
> constraints.

> To speed things up, we really need to special case insertions without  
> triggers and constraints, [probably allow for unique constraints],  

Do you have any profiling data to back up these assertions?  I haven't
noticed that firing zero tuples takes any visible percentage of COPY
time.

			regards, tom lane