Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl>, Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit
Date: 2001-10-22 05:56:54
Message-ID: 3BD3B526.CD8FBEAF@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

(switched thread to hackers)

> ... If the 'tip' is localized to a few lines, usually in
> gram.y, I don't see a reason not to help people find the right answer.
> It helps them and reduces redundant bug repots. I can't imagine a
> reason not to do it unless it starts to make our code more complex.

I'm with Peter on this one. I'd like to *not* clutter up the code and
error reporting with hints and suggestions which may or may not be to
the point.

We *should* have docs which list error messages and possible solutions,
and throwing that info into code is a poor second choice imho.

- Thomas

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Markus Wagner 2001-10-22 07:37:02 where are the memory leaks?
Previous Message Thomas Lockhart 2001-10-22 05:51:42 Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit

Browse pgsql-hackers by date

  From Date Subject
Next Message Reiner Dassing 2001-10-22 06:42:40 Index of a table is not used (in any case)
Previous Message Thomas Lockhart 2001-10-22 05:51:42 Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit