| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: add modulo (%) operator to pgbench |
| Date: | 2015-03-03 20:43:02 |
| Message-ID: | CA+Tgmoa6v_qwEy_p1HG-ZnPF59CfoNKa8UO_0Hv1YVvTsiBuJQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 2, 2015 at 5:41 PM, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>> but I'd like to have a more robust discussion about what we want the error
>> reporting to look like rather than just sliding it into this patch.
>
> As an input, I suggest that the error reporting feature should provide a
> clue about where the issue is, including a line number and possibly the
> offending line. Not sure what else is needed.
I agree. But I think it might be better to try to put everything
related to a single error on one line, in a consistent format, e.g.:
bad.sql:3: syntax error in set command at column 25
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-03-03 20:49:06 | Re: Idea: GSoC - Query Rewrite with Materialized Views |
| Previous Message | Andrew Dunstan | 2015-03-03 20:36:07 | Re: Patch: raise default for max_wal_segments to 1GB |