| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Akim Demaille <akim(at)lrde(dot)epita(dot)fr>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove useless associativity/precedence from parsers |
| Date: | 2019-05-23 03:34:45 |
| Message-ID: | CA+TgmoatPhGjfkHke_7VKPu9kZjDGkwNZNFHvwHoO++xF8KTXA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 21, 2019 at 3:07 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Other PG hackers might have a different laundry list, but that's mine.
Good list.
Another thing is that it would be nice to have a better way of
resolving conflicts than attaching precedence declarations. Some
problems can't be solved that way at all, and others can only be
solved that way at the risk of unforeseen side effects. One possible
idea is a way to mark a rule %weak, meaning that it should only be
used if no non-%weak rule could apply. I'm not sure if that would
really be the best way, but it's one idea. A more general version
would be some kind of ability to give rules different strengths; in
the case of a grammar conflict, the "stronger" rule would win.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2019-05-23 03:49:57 | Re: Patch to fix write after end of array in hashed agg initialization |
| Previous Message | Jonathan S. Katz | 2019-05-23 03:30:49 | Re: PostgreSQL 12 Beta 1 press release draft |