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

From Hannu Krosing
Subject Re: [PERFORM] psql -A (unaligned format) eats too much
Date
Msg-id 1149597013.3818.7.camel@localhost.localdomain
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
Ühel kenal päeval, E, 2006-06-05 kell 14:10, kirjutas Tom Lane:
> Neil Conway <neilc@samurai.com> writes:
> > On Mon, 2006-06-05 at 19:17 +0200, Zoltan Boszormenyi wrote:
> >> The general case cannot be applied for all particular cases.
> >> E.g. you cannot use cursors from shell scripts
> 
> > This could be fixed by adding an option to psql to transparently produce
> > SELECT result sets via a cursor.

I think this is an excellent idea. 

psql --cursor --fetchby 10000 -c "select ..." | myprogram

> 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 ?

even without --cursor there is still no very good way to find out when
something else goes wrong, like the result inside libpq taking up all
memory and so psql runs out of memory on formatting some longer lines.


-- 
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia

Skype me:  callto:hkrosing
Get Skype for free:  http://www.skype.com




pgsql-hackers by date:

Previous
From: "Mark Woodward"
Date:
Subject: How to avoid transaction ID wrap
Next
From: Heikki Linnakangas
Date:
Subject: Re: How to avoid transaction ID wrap