Doc: use "an SQL" consistently rather than "a SQL"

Per the precedent set by 04539e73f, adjust article prefixes for "SQL" to
use "an" consistently rather than "a", i.e., "an es-que-ell" rather than
"a sequel".

Also see b51f86e49, b1b13d2b5, d866f0374 and 7bdd489d3.

Author: David Rowley <dgrowleyml@gmail.com>
Discussion: https://postgr.es/m/CAApHDvp3osQwQam+wNTp9BdhP+QfWO6aY6ZTixQQMfM-UArKCw@mail.gmail.com
This commit is contained in:
David Rowley 2026-04-12 22:49:27 +12:00
parent 80156cee06
commit a78cf591a3

View file

@ -4230,7 +4230,7 @@ supportfn(internal) returns internal
the <literal>FROM</literal> item as though a sub-select had been
written instead. The Query tree must appear as it would after parse
analysis and rewrite processing. One way to ensure that that's true
is to build a SQL string then feed it
is to build an SQL string then feed it
through <function>pg_parse_query</function>
and <function>pg_analyze_and_rewrite</function>, or related
functions. <literal>PARAM_EXTERN</literal> <structname>Param</structname>