On Thu, Jan 06, 2022 at 08:52:23AM +0100, Pavel Stehule wrote:
>
> I am not sure if there is enough agreement and if there is enough necessity
> for this feature.
>
> In this discussion there were more general questions about future
> development of plpgsql (about possible configurations and compiler
> parametrizations, and how to switch the configuration on global and on
> local levels). This is not fully solved yet. This is probably the reason
> why discussion about this specific feature (and very simple feature) has
> not reached a clear end. Generally, this is the same problem in Postgres.
I agree, but on the other hand I don't see how defining a top level block
alias identical for every single plpgsql function would really make sense.
Not every function has a very long name and would benefit from it, and no one
can really assume that e.g. "root" or whatever configured name won't be used in
any plpgsql function on that database or cluster. So while having some global
configuration infrastructure can be useful I still don't think that it could be
used for this purpose.
Anyway, the only committer that showed some interest in the feature is Michael,
and he seemed ok in principle with the "alias-implementation" approach.
Michael, did you have a look at this version ([1]), or do you think it should
simply be rejected?
[1]: https://www.postgresql.org/message-id/attachment/120789/plpgsql-routine-label-option-alias-implementation.patch
