Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TVQVn-0001Sb-77 for pgsql-hackers@postgresql.org; Mon, 05 Nov 2012 17:30:59 +0000 Received: from hogranch.com ([75.101.82.47]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TVQVl-00023L-1u for pgsql-hackers@postgresql.org; Mon, 05 Nov 2012 17:30:58 +0000 Received: from [192.168.0.2] (porker [192.168.0.2]) by hogranch.com (8.11.6/8.11.6) with ESMTP id qA5HUZ925526 for ; Mon, 5 Nov 2012 09:30:35 -0800 Message-ID: <5097F7B6.4040300@hogranch.com> Date: Mon, 05 Nov 2012 09:30:30 -0800 From: John R Pierce User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: pgsql-hackers@postgresql.org Subject: Re: [PERFORM] out of memory References: <20121030.190859.2262955278129522321.t-ishii@sraoss.co.jp> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HawgScanner-Information: Please contact the ISP for more information X-HawgScanner: Found to be clean X-Pg-Spam-Score: -2.3 (--) X-Archive-Number: 201211/121 X-Sequence-Number: 215973 On 11/05/12 9:27 AM, Robert Haas wrote: > That is, if we have a large datum that we're trying to > send back to the client, could we perhaps chop off the first 50MB or > so, do the encoding on that amount of data, send the data to the > client, lather, rinse, repeat? I'd suggest work_mem sized chunks for this? -- john r pierce N 37, W 122 santa cruz ca mid-left coast