| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)skype(dot)net> |
| 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 13:48:43 |
| Message-ID: | 15738.1149601723@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Hannu Krosing <hannu(at)skype(dot)net> writes:
> hel kenal peval, 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.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2006-06-06 13:53:25 | Re: table/index fillfactor control |
| Previous Message | Tom Lane | 2006-06-06 13:45:41 | Re: Why do we want to %Remove behavior of postmaster -o |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-06 14:23:55 | Re: How to force Postgres to use index on ILIKE |
| Previous Message | Hannu Krosing | 2006-06-06 12:30:12 | Re: [PERFORM] psql -A (unaligned format) eats too much |