| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "CK Tan" <cktan(at)greenplum(dot)com> |
| Cc: | "Luke Lonergan" <llonergan(at)greenplum(dot)com>, "Simon Riggs" <simon(at)enterprisedb(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>, "Jeff Davis" <pgsql(at)j-davis(dot)com> |
| Subject: | Re: Seq scans roadmap |
| Date: | 2007-05-13 23:54:24 |
| Message-ID: | 21639.1179100464@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"CK Tan" <cktan(at)greenplum(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-05-14 01:55:01 | Re: Concurrent psql patch |
| Previous Message | CK Tan | 2007-05-13 23:41:29 | Re: Seq scans roadmap |