On Monday, December 13, 2021, Bryn Llewellyn <bryn@yugabyte.com> wrote:
There must be a reason to prefer a “language sql” procedure over a “language plpgsql” procedure—otherwise the former wouldn’t be supported.
I would say that is true for functions. I wouldn’t assume that for procedures - it’s probable that because sql already worked for functions we got that feature for free when implementing procedures.