From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Erki Eessaar <erki(dot)eessaar(at)taltech(dot)ee>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: SQL-standard function bodies and creating SECURITY DEFINER routines securely |
Date: | 2022-08-16 19:38:13 |
Message-ID: | YvvyJTmSbPLKUm5k@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, Aug 16, 2022 at 03:34:22PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I have written the attached patch to mention this issue about sql_body
> > functions.
>
> Spell-check, please. Seems OK otherwise.
Just when I think I didn't add enough text to warrant a spell check.
:-( Updated patch attached.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
Attachment | Content-Type | Size |
---|---|---|
function.diff | text/x-diff | 913 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Erwin Brandstetter | 2022-08-16 21:09:59 | Confusing bit in the "EXAMPLES" section for INSERT |
Previous Message | Tom Lane | 2022-08-16 19:34:22 | Re: SQL-standard function bodies and creating SECURITY DEFINER routines securely |