Re: Why can't I have a "language sql" anonymous block?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Bryn Llewellyn <bryn(at)yugabyte(dot)com>
Cc: Tom Lane PostgreSQL <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Why can't I have a "language sql" anonymous block?
Date: 2021-12-14 22:58:49
Message-ID: CAKFQuwa0XH7bQxycTSw8FiBbwcsEKxOSKZt=q-XemfR0uyjyZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday, December 13, 2021, Bryn Llewellyn <bryn(at)yugabyte(dot)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.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2021-12-14 23:17:16 Re: When Update balloons memory
Previous Message Tom Lane 2021-12-14 22:51:18 Re: Properly handling aggregate in nested function call