From: | Hannu Krosing <hannu(at)skype(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, Zoltan Boszormenyi <zboszor(at)dunaweb(dot)hu>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Mark Woodward <pgsql(at)mohawksoft(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PERFORM] psql -A (unaligned format) eats too much |
Date: | 2006-06-06 12:30:12 |
Message-ID: | 1149597013.3818.7.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Ühel kenal päeval, E, 2006-06-05 kell 14:10, kirjutas Tom Lane:
> Neil Conway <neilc(at)samurai(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Woodward | 2006-06-06 12:42:50 | How to avoid transaction ID wrap |
Previous Message | Kenneth Marshall | 2006-06-06 11:58:10 | Re: Duplicate rows sneaking in despite PRIMARY KEY / UNIQUE constraint |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-06-06 13:48:43 | Re: [PERFORM] psql -A (unaligned format) eats too much |
Previous Message | Andrus | 2006-06-06 09:57:31 | Re: How to force Postgres to use index on ILIKE |