X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B29159FA43C for ; Tue, 6 Jun 2006 10:49:10 -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 96789-05 for ; Tue, 6 Jun 2006 10:49:02 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2CCDD9F9316 for ; Tue, 6 Jun 2006 10:49:01 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k56DmhQP015739; Tue, 6 Jun 2006 09:48:43 -0400 (EDT) To: Hannu Krosing cc: Neil Conway , Zoltan Boszormenyi , Andrew Dunstan , Mark Woodward , "Jim C. Nasby" , pgsql-hackers@postgresql.org Subject: Re: [PERFORM] psql -A (unaligned format) eats too much In-reply-to: <1149597013.3818.7.camel@localhost.localdomain> References: <44835834.2020309@dunaweb.hu> <44835F86.5040008@dunaweb.hu> <20060605152258.GT53487@pervasive.com> <20512.1149521250@sss.pgh.pa.us> <20060605155349.GU53487@pervasive.com> <20813.1149523235@sss.pgh.pa.us> <18006.24.91.171.78.1149526092.squirrel@mail.mohawksoft.com> <44845E86.3080001@dunslane.net> <4484672B.8080606@dunaweb.hu> <1149529945.5577.5.camel@localhost> <21820.1149531024@sss.pgh.pa.us> <1149597013.3818.7.camel@localhost.localdomain> Comments: In-reply-to Hannu Krosing message dated "Tue, 06 Jun 2006 15:30:12 +0300" Date: Tue, 06 Jun 2006 09:48:43 -0400 Message-ID: <15738.1149601723@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/189 X-Sequence-Number: 84422 Hannu Krosing writes: > Ühel kenal päeval, E, 2006-06-05 kell 14:10, kirjutas Tom Lane: >> Note of course that such a thing would push the incomplete-result >> problem further upstream. For instance in (hypothetical --cursor >> switch) >> psql --cursor -c "select ..." | myprogram >> there would be no very good way for myprogram to find out that it'd >> been sent an incomplete result due to error partway through the SELECT. > would it not learn about it at the point of error ? No, it would merely see EOF after some number of result rows. (I'm assuming you're also using -A -t so that the output is unadorned.) regards, tom lane