| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: improve pgbench syntax error messages |
| Date: | 2015-03-07 10:49:24 |
| Message-ID: | alpine.DEB.2.10.1503071145120.24480@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Here is a v3, which (1) activates better error messages from bison
> and (2) improves the error reporting from the scanner as well.
v4.
While adding a basic function call syntax to expressions, a noticed that
it would be useful to access the "detail" field of syntax errors so as to
report the name of the unknown function. This version just adds the hook
(expr_yyerror_detailed) that could be called later for this purpose.
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| pgbench-expr-error-4.patch | text/x-diff | 9.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-03-07 12:34:42 | Re: Improving test coverage of extensions with pg_dump |
| Previous Message | Noah Misch | 2015-03-07 06:48:28 | Re: Question about lazy_space_alloc() / linux over-commit |