From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-19 21:41:36 |
Message-ID: | 44BEA710.6060700@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers pgsql-patches |
Joe Conway wrote:
> Tom Lane wrote:
>
>> Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com> writes:
>>
>>> Strange. Last time I checked I thought MySQL dump used 'multivalue
>>> lists in inserts' for dumps, for the same reason that we use COPY
>>
>> I think Andrew identified the critical point upthread: they don't try
>> to put an unlimited number of rows into one INSERT, only a megabyte
>> or so's worth. Typical klugy-but-effective mysql design approach ...
>
> OK, so given that we don't need to be able to do 1 million
> multi-targetlist insert statements, here is rev 2 of the patch.
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?
If we do, I'll start looking for a new rev 3 strategy (ideas/pointers
etc very welcome). If not, I'll start working on docs and regression test.
Thanks,
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-20 03:58:07 | Re: [PATCHES] 8.2 features? |
Previous Message | Peter Eisentraut | 2006-07-19 16:54:22 | Re: I'd like to translate the english manual into Korean! |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-19 21:53:40 | Re: pg_regress breaks on msys |
Previous Message | Oleg Bartunov | 2006-07-19 21:26:28 | Re: contrib/hstore - missing, deleted or not material for |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-19 21:53:40 | Re: pg_regress breaks on msys |
Previous Message | Tom Lane | 2006-07-19 21:05:07 | Re: pg_regress breaks on msys |