| From: | Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Joe Conway <mail(at)joeconway(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>, Susanne Ebrecht <susanne(dot)ebrecht(at)credativ(dot)de> |
| Subject: | Re: [HACKERS] 8.2 features? |
| Date: | 2006-07-19 01:20:29 |
| Message-ID: | 44BD88DD.7070507@calorieking.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers pgsql-patches |
> I did some experimentation just now, and could not get mysql to accept a
> command longer than about 1 million bytes. It complains about
> Got a packet bigger than 'max_allowed_packet' bytes
> which seems a bit odd because max_allowed_packet is allegedly set to
> 16 million, but anyway I don't think people are going to be loading any
> million-row tables using single INSERT commands in mysql either.
Ah no, I'm mistaken. It's not by default in mysqldump, but it does seem
"recommended". This is from "man mysqldump":
-e|--extended-insert
Allows utilization of the new, much faster INSERT syntax.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-19 03:32:34 | Re: [HACKERS] 8.2 features? |
| Previous Message | Christopher Kings-Lynne | 2006-07-19 01:18:12 | Re: [HACKERS] 8.2 features? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2006-07-19 01:52:42 | Re: Progress bar updates |
| Previous Message | Christopher Kings-Lynne | 2006-07-19 01:18:12 | Re: [HACKERS] 8.2 features? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-19 02:46:04 | Re: pg_regress in C |
| Previous Message | Christopher Kings-Lynne | 2006-07-19 01:18:12 | Re: [HACKERS] 8.2 features? |