| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgcrypto.sgml: built in -> built-in |
| Date: | 2026-08-16 16:21:33 |
| Message-ID: | aoHiJI3TTDN13bbt@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
On 2026-Aug-16, Erik Rijkers wrote:
> The documentation contains the word 'built-in' (with hyphen) more than 200
> times so let's correct the 2x 'built in' in doc/src/sgml/pgcrypto.sgml
Well observed. We do have "builtin" a number of times though. Do we
want to change those too? For example
contrib/pgcrypto/pgcrypto.c- DefineCustomEnumVariable("pgcrypto.builtin_crypto_enabled",
contrib/pgcrypto/pgcrypto.c: "Sets if builtin crypto functions are enabled.",
contrib/pgcrypto/pgcrypto.c: "\"on\" enables builtin crypto, \"off\" unconditionally disables and \"fips\" "
contrib/pgcrypto/pgcrypto.c: "will disable builtin crypto if OpenSSL is in FIPS mode",
contrib/pgcrypto/pgcrypto.c- &builtin_crypto_enabled,
--
contrib/postgres_fdw/deparse.c- * If the constant has nondefault collation, either it's of a
contrib/postgres_fdw/deparse.c: * non-builtin type, or it reflects folding of a CollateExpr.
contrib/postgres_fdw/deparse.c- * It's unsafe to send to the remote unless it's used in a
--
contrib/postgres_fdw/option.c- /*
contrib/postgres_fdw/option.c: * Disallow OAuth options for now, since the builtin flow communicates
contrib/postgres_fdw/option.c- * on stderr by default and can't cache tokens yet.
--
contrib/test_decoding/test_decoding.c- *
contrib/test_decoding/test_decoding.c: * Some builtin types aren't quoted, the rest is quoted. Escaping is done
contrib/test_decoding/test_decoding.c- * per standard SQL rules.
doc/src/sgml/jit.sgml- <para>
doc/src/sgml/jit.sgml: <productname>PostgreSQL</productname> has builtin support to perform
doc/src/sgml/jit.sgml- <acronym>JIT</acronym> compilation using <ulink
--
doc/src/sgml/libpq.sgml- installation documentation</link> for information on how to enable support
doc/src/sgml/libpq.sgml: for Device Authorization as a builtin flow.
doc/src/sgml/libpq.sgml- </para>
There's a bunch we should leave alone, but the ones I quote above and a
few more are less clear to me (and I suspect we should also change to
"built-in").
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-08-16 16:21:59 | Residual tsquery cleanups |
| Previous Message | Tom Lane | 2026-08-16 15:59:31 | Re: examine_variable ignored CollateExpr |