Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] psql -A (unaligned format) eats too much

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: 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-05 18:10:24
Message-ID: 21820.1149531024@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-performance
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.

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.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Chris BeecroftDate: 2006-06-05 19:05:08
Subject: Some queries starting to hang
Previous:From: Neil ConwayDate: 2006-06-05 17:52:25
Subject: Re: [PERFORM] psql -A (unaligned format) eats too much

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-06-05 18:57:11
Subject: Re: adding new field
Previous:From: Jonah H. HarrisDate: 2006-06-05 18:05:09
Subject: Re: adding new field

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group