Re: Selecting large tables gets killed - Mailing list pgsql-hackers

From Bernd Helmle
Subject Re: Selecting large tables gets killed
Date
Msg-id E2DBCFEEAE18C1FE69040BC3@apophis.credativ.lan
Whole thread Raw
In response to Re: Selecting large tables gets killed  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Selecting large tables gets killed  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List pgsql-hackers

--On 20. Februar 2014 09:51:47 -0500 Tom Lane <tgl@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: WAL Rate Limiting
Next
From: Hannu Krosing
Date:
Subject: Re: WAL Rate Limiting