Re: [PERFORM] psql -A (unaligned format) eats too much - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: [PERFORM] psql -A (unaligned format) eats too much
Date
Msg-id 20060606143918.GA53487@pervasive.com
Whole thread Raw
In response to Re: [PERFORM] psql -A (unaligned format) eats too much  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PERFORM] psql -A (unaligned format) eats too much  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Jun 06, 2006 at 09:48:43AM -0400, Tom Lane wrote:
> Hannu Krosing <hannu@skype.net> 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.)

So if an error occurs partway through reading a cursor, no error message
is generated? That certainly sounds like a bug to me...
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: fillfactor using WITH syntax
Next
From: Tom Lane
Date:
Subject: Re: [PERFORM] psql -A (unaligned format) eats too much