On Thu, Jan 6, 2022, at 17:55, Tom Lane wrote: > Even if it works today, we could be letting ourselves in for future > trouble. The SQL standard is a moving target, and they could easily > standardize some future syntax involving IN that creates a problem here.
Perhaps the "in." notation could be standardized by the SQL standard, allowing vendors to use such notation without fear of future trouble? > I think we already have two perfectly satisfactory answers: > * qualify parameters with the function name to disambiguate them; > * use the ALIAS feature to create an internal, shorter name. I would say we have two OK workarounds, far from perfect: * Qualifying parameters is too verbose. Function names can be long. * Having to remap parameters using ALIAS is cumbersome. This problem is one of my top annoyances with PL/pgSQL. /Joel
