X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 4AE049F95E3 for ; Tue, 18 Jul 2006 18:36:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 00215-04 for ; Tue, 18 Jul 2006 21:36:34 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by postgresql.org (Postfix) with ESMTP id A4F279F94F3 for ; Tue, 18 Jul 2006 18:36:35 -0300 (ADT) Received: by nf-out-0910.google.com with SMTP id p77so5874nfc for ; Tue, 18 Jul 2006 14:36:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=AnjC7oY/rpmxrD8gLVM5zWBWKAWYwUYL7JZl2m24N7b6m3N4N2iFMuStmInIoYtVS7LBkB6RIA+312HlOEyMeyeQvApyi7YvAr5tHE5RBEnAWGJVzWxJwa6tM0uiIW0lqjFe7r9p867S2lHDGNmRG34dns+jDm3KJktbHpWH+/k= Received: by 10.48.108.19 with SMTP id g19mr1078709nfc; Tue, 18 Jul 2006 14:36:34 -0700 (PDT) Received: from ?192.168.0.4? ( [88.64.64.81]) by mx.gmail.com with ESMTP id o45sm768722nfa.2006.07.18.14.36.33; Tue, 18 Jul 2006 14:36:33 -0700 (PDT) Message-ID: <44BD5508.3050504@gmail.com> Date: Tue, 18 Jul 2006 23:39:20 +0200 From: Thomas Bley User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: pgsql-hackers@postgresql.org Subject: Re: [PATCHES] 8.2 features? 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> In-Reply-To: <5842.1153246741@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/731 X-Sequence-Number: 86586 from http://dev.mysql.com/doc/refman/4.1/en/blob.html You can change the message buffer size by changing the value of the max_allowed_packet variable, but you must do so for both the server and your client program. For example, both mysql and mysqldump allow you to change the client-side max_allowed_packet value. Tom Lane wrote: >>> If the use case is people running MySQL dumps, then there will be >>> millions of values-targetlists in MySQL dumps. >>> > > 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. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings > >