| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Bernd Helmle <mailings(at)oopsware(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Susanne Ebrecht <susanne(dot)ebrecht(at)credativ(dot)de> |
| Subject: | Re: [PATCHES] 8.2 features? |
| Date: | 2006-07-20 03:58:07 |
| Message-ID: | 23198.1153367887@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers pgsql-patches |
Joe Conway <mail(at)joeconway(dot)com> writes:
> I did some testing today against mysql and found that it will easily
> absorb insert statements with 1 million targetlists provided you set
> max_allowed_packet high enough for the server. It peaked out at about
> 600MB, compared to my test similar last night where it was using about
> 3.8 GB when I killed it.
> So the question is, do we care?
What's the performance like relative to mysql? It seems hard to believe
that we can afford the overhead of a separate INSERT statement per row
(duplicating all the work of parse analysis, rewrite, planning, executor
start/stop) ... at least not without looking mighty bad.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2006-07-20 04:16:02 | Re: [PATCHES] 8.2 features? |
| Previous Message | Joe Conway | 2006-07-19 21:41:36 | Re: [PATCHES] 8.2 features? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2006-07-20 04:16:02 | Re: [PATCHES] 8.2 features? |
| Previous Message | Tom Lane | 2006-07-20 03:34:03 | Re: Statement Queuing |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2006-07-20 04:16:02 | Re: [PATCHES] 8.2 features? |
| Previous Message | Andrew Dunstan | 2006-07-20 02:57:40 | Re: pg_regress breaks on msys |