Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit
Date
Msg-id 3BD3B526.CD8FBEAF@fourpalms.org
Whole thread Raw
Responses Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit
Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit
List 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


pgsql-hackers by date:

Previous
From: "Johann Zuschlag"
Date:
Subject: Re: Error while restoring database
Next
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit