Re: PostgreSQL-13.3 parser.y with positional references by named references - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: PostgreSQL-13.3 parser.y with positional references by named references
Date
Msg-id 26189a69-2612-dcca-dcc6-b931f8639ea7@enterprisedb.com
Whole thread Raw
In response to Re: PostgreSQL-13.3 parser.y with positional references by named references  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PostgreSQL-13.3 parser.y with positional references by named references  (ilmari@ilmari.org (Dagfinn Ilmari Mannsåker))
List pgsql-hackers
On 04.07.21 17:58, Tom Lane wrote:
> Domingo Alvarez Duarte <mingodad@gmail.com> writes:
>> Here https://gist.github.com/mingodad/49291e0e9505522c66fcd3fcea4a939d I
>> posted the postgresql-13.3/src/backend/parser/gram.y with positional
>> references by named references that is supported by bison for some time now.
> 
> When is "some time now"?

release 2.5 (2011-05-14)

> I do see the point about it being annoying to update $N references
> when a rule is changed.  But this solution has enough downsides that
> I'm not sure it's a net win.  Maybe if it were applied selectively,
> to just the longer DDL productions, it'd be worth doing?

I agree that it should be applied selectively.



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: trivial improvement to system_or_bail
Next
From: Peter Eisentraut
Date:
Subject: Re: "debug_invalidate_system_caches_always" is too long