Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 317B263271B for ; Tue, 15 Jun 2010 09:21:45 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 08142-04 for ; Tue, 15 Jun 2010 12:21:34 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtpcorp.com (smtpcorp.com [67.192.120.76]) by mail.postgresql.org (Postfix) with ESMTP id A08D9632698 for ; Tue, 15 Jun 2010 09:21:34 -0300 (ADT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=main; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:Message-ID:Date:Subject:From:To; bh=V4lxViQlsPH/OXJg7UHVttdkGdKz+uotPrf49Obd1/A=; b=Pn+6x/pTyZ31V240+Hyxgjy4zvm4pPr9hTL7ybRhOdPg33dfe38vtwzb4Ai0JreIGkcBtN859Ls7n/LcD5VwPT7oVt5XQpiMjWnGXXOsI53RWM7bSoI0Zeyr99OAOYJw; Received: from ip-118-90-143-50.xdsl.xnet.co.nz ([118.90.143.50] helo=gonzo) by smtpcorp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.70) id 1OOV92-0008VC-Ia; mid 144 for pgsql-php@postgresql.org; Tue, 15 Jun 2010 12:21:09 +0000 Received: from news by gonzo with local (Exim 4.69) (envelope-from ) id 1OOV8q-0007Hn-On for pgsql-php@postgresql.org; Wed, 16 Jun 2010 00:21:20 +1200 To: pgsql-php@postgresql.org Path: not-for-mail From: Jasen Betts Newsgroups: gmane.comp.db.postgresql.php Subject: Re: large resultset Date: 15 Jun 2010 12:21:20 GMT Organization: Dis (not Dat) Organisation Lines: 29 Message-ID: References: <8f468dc246fb6075f2a1f46b09f71a6d@xs4all.nl> <1276598244.3820.16204.camel@happy.home.mcmillan.net.nz> NNTP-Posting-Host: localhost Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: reversiblemaps.ath.cx 1276604480 25114 127.0.0.1 (15 Jun 2010 12:21:20 GMT) X-Face: ?)Aw4rXwN5u0~$nqKj`xPz>xHCwgi^q+^?Ri*+R(&uv2=E1Q0Zk(>h!~o2ID@6{uf8s; a +M[5[U[QT7xFN%^gR"=tuJw%TXXR'Fp~W; (T"1(739R%m0Yyyv*gkGoPA.$b,D.w:z+<'"=-lVT?6 {T?=R^:W5g|E2#EhjKCa+nt":4b}dU7GYB*HBxn&Td$@f%.kl^:7X8rQWd[NTc"P"u6nkisze/Q; 8 "9Z{peQF,w)7UjV$c|RO/mQW/NMgWfr5*$-Z%u46"/00mx-,\R'fLPe.)^ User-Agent: slrn/pre1.0.0-2 (Linux) X-Smtpcorp-Track: 4509933.1.50930009 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.8 tagged_above=-10 required=5 tests=BAYES_50=0.8 X-Spam-Level: X-Archive-Number: 201006/10 X-Sequence-Number: 4149 On 2010-06-15, Andrew McMillan wrote: > Fundamentally sending 2million of anything can get problematic pretty > darn quickly, unless the 'thing' is less than 100 bytes. > > My personal favourite would be to write a record somewhere saying 'so > and so wants these 2 million records', and give the user a URL where > they can fetch them from. Or e-mail them to the user, or... just about > anything, except try and generate them in-line with the page, in a > reasonable time for their browser to not give up, or their proxy to not > give up, or their ISP's transparent proxy to not give up. email often fails for sizes over 10Mb > Why do they want 2 million record anyway? 2 million of what? Will > another user drop by 10 seconds later and also want 2 million records? > The same 2 million? Why does the user want 2 million records? Is there > something that can be done to the 2 million records to make them a > smaller but more useful set of information? /Nobody/ wants a web page with 2 million lines on it, (scrolling gets tricky when each pixel is 2000 lines of data, plus most browsers aren't designed to handle it well) still if it's served with "Content-Disposition: Attachment" they'll get offered it for download instead. (unless they use IE and you use cookies and SSL in which case it doesn't work)