On Tue, May 21, 2019 at 3:07 PM Tom Lane <t...@sss.pgh.pa.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
