Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 2BB39B5DC02 for ; Wed, 20 Jul 2011 11:53:50 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 01425-05 for ; Wed, 20 Jul 2011 14:53:44 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mail.postgresql.org (Postfix) with ESMTP id 17CDAB5DC01 for ; Wed, 20 Jul 2011 11:53:43 -0300 (ADT) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QjY9c-00042x-VP for pgsql-admin@postgresql.org; Wed, 20 Jul 2011 16:53:40 +0200 Received: from 80.150.102.194 ([80.150.102.194]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Jul 2011 16:53:40 +0200 Received: from spam_eater by 80.150.102.194 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Jul 2011 16:53:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: Thomas Kellerer Subject: Re: Problem retrieving large records (bytea) data from a table Date: Wed, 20 Jul 2011 16:53:51 +0200 Lines: 14 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 80.150.102.194 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 In-Reply-To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.148 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_SORBS_WEB=0.77, RCVD_NUMERIC_HELO=1.164, RP_MATCHES_RCVD=-1.193, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201107/145 X-Sequence-Number: 37924 jtkells@verizon.net, 05.07.2011 18:44: > A while ago the some developers inserted several records with a > document (stored in doc_Data) that was around 400 - 450 MB each. Now > when you do a select * (all) from this table you get a hang and the > system becomes unresponsive. What application/program is "hanging"? The client that retrieves the data or PostgreSQL itself? > So I'm not sure how to find these bad records and why I am getting a > hang. If your client application is hanging, I don't think there is a single "bad" record, it just chokes on the size of the result set. Regards Thomas