| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-05 18:57:11 | Re: adding new field |
| Previous Message | Jonah H. Harris | 2006-06-05 18:05:09 | Re: adding new field |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Beecroft | 2006-06-05 19:05:08 | Some queries starting to hang |
| Previous Message | Neil Conway | 2006-06-05 17:52:25 | Re: [PERFORM] psql -A (unaligned format) eats too much |