On Tue, 11 Apr 2023 at 17:43, David Rowley <dgrowle...@gmail.com> wrote:
>
> On Fri, 11 Jun 2021 at 13:44, David Rowley <dgrowle...@gmail.com> wrote:
> > Anyway, I'll set an alarm for this time next year so I can check on
> > how many inconsistencies have crept back in over the development
> > cycle.
>
> That alarm went off today.
>
> There seem to be only 3 "a SQL"s in the docs to change to "an SQL".
>
> This is a pretty old thread, so here's a link [1] to the discussion.
>
> [1]
> https://postgr.es/m/caaphdvpml27uqfxnryo1mjddskvmqoizispvsaghke_tskx...@mail.gmail.com
Link to the old thread above.
There's just 1 instance of "a SQL" that crept into PG16 after
d866f0374. This probably means I'd be better off doing this in June a
few weeks before branching...
Patch attached.
David
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 8ff9a520ca..2aa25f62f5 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -5479,7 +5479,7 @@ CREATE FUNCTION get_color_note (rainbow) RETURNS text AS
</para>
<para>
- On the other hand, for a SQL-language function or procedure whose body
+ On the other hand, for an SQL-language function or procedure whose body
is written in SQL-standard style, the body is parsed at function
definition time and all dependencies recognized by the parser are
stored. Thus, if we write the function above as
