X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id EF5169FA379 for ; Tue, 18 Jul 2006 20:42:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 37784-05 for ; Tue, 18 Jul 2006 20:41:51 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by postgresql.org (Postfix) with ESMTP id 27E969FA25A for ; Tue, 18 Jul 2006 20:41:51 -0300 (ADT) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 3CCFB53; Tue, 18 Jul 2006 18:41:50 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 20D9C61C5A; Tue, 18 Jul 2006 18:41:49 -0500 (CDT) Date: Tue, 18 Jul 2006 18:41:49 -0500 From: "Matthew D. Fuller" To: Tom Lane Cc: pgsql-hackers@postgresql.org Subject: Re: [PATCHES] 8.2 features? Message-ID: <20060718234149.GV98476@over-yonder.net> References: <44B69778.5050104@dunslane.net> <50461.84.63.113.55.1152832991.squirrel@pezone.net> <44B7ADFC.90205@dunslane.net> <44BC0432.3040509@joeconway.com> <44BC661F.80609@joeconway.com> <44BCD06C.3060409@calorieking.com> <44BCF1D4.3010807@dunslane.net> <5842.1153246741@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5842.1153246741@sss.pgh.pa.us> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/743 X-Sequence-Number: 86598 On Tue, Jul 18, 2006 at 02:19:01PM -0400 I heard the voice of Tom Lane, and lo! it spake thus: > > 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. On the contrary, I've hit it several times by just trying to import [into another database] the output of a mysqldump I just did. Great design, that... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.