| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marti Raudsepp <marti(at)juffo(dot)org> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, amul sul <sul_amul(at)yahoo(dot)co(dot)in>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Selecting large tables gets killed |
| Date: | 2014-02-20 15:30:21 |
| Message-ID: | E2DBCFEEAE18C1FE69040BC3@apophis.credativ.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On 20. Februar 2014 09:51:47 -0500 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Yeah. The other reason that you can't just transparently change the
> behavior is error handling: people are used to seeing either all or
> none of the output of a query. In single-row mode that guarantee
> fails, since some rows might get output before the server detects
> an error.
That's true. I'd never envisioned to this transparently either, exactly of
this reason. However, i find to have single row mode somewhere has some
attractiveness, be it only to have some code around that shows how to do it
right. But i fear we might complicate things in psql beyond what we really
want.
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2014-02-20 16:01:15 | Re: WAL Rate Limiting |
| Previous Message | Robert Haas | 2014-02-20 15:22:11 | Re: WAL Rate Limiting |