On 08/16/2011 04:56 AM, Magnus Hagander wrote:
On Mon, Aug 15, 2011 at 23:49, Greg Stark<st...@mit.edu> wrote:
On Mon, Aug 15, 2011 at 9:31 PM, Tom Lane<t...@sss.pgh.pa.us> wrote:
... and that would be a seriously bad API. There are not SUSET
restrictions on other resources such as work_mem. Why do we need
one for this?
I think a better analogy would be imposing a maximum number of rows a
query can output. That might be a sane thing to have for some
circumstances but it's not useful in general.
Uh. You mean like LIMIT, which we already have?
There is no LIMIT imposed on a query by a server setting, which would be
the right analogy here.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
