postgresql/contrib
Peter Eisentraut 17974ec259 Revise GUC names quoting in messages again
After further review, we want to move in the direction of always
quoting GUC names in error messages, rather than the previous (PG16)
wildly mixed practice or the intermittent (mid-PG17) idea of doing
this depending on how possibly confusing the GUC name is.

This commit applies appropriate quotes to (almost?) all mentions of
GUC names in error messages.  It partially supersedes a243569bf6 and
8d9978a717, which had moved things a bit in the opposite direction
but which then were abandoned in a partial state.

Author: Peter Smith <smithpb2250@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/CAHut%2BPv-kSN8SkxSdoHano_wPubqcg5789ejhCDZAcLFceBR-w%40mail.gmail.com
2024-05-17 11:44:26 +02:00
..
amcheck Fix an assortment of typos 2024-05-04 02:33:25 +12:00
auth_delay
auto_explain
basebackup_to_shell
basic_archive Add built-in ERROR handling for archive callbacks. 2024-04-02 22:28:11 -05:00
bloom
bool_plperl
btree_gin
btree_gist Revert temporal primary keys and foreign keys 2024-05-16 08:17:46 +02:00
citext Skip citext_utf8 test on Windows. 2024-05-13 07:55:58 +12:00
cube
dblink Make libpqsrv_cancel's return const char *, not char * 2024-04-05 18:23:10 +02:00
dict_int
dict_xsyn
earthdistance
file_fdw
fuzzystrmatch
hstore Use new overflow-safe integer comparison functions. 2024-02-16 14:05:36 -06:00
hstore_plperl
hstore_plpython
intagg
intarray Use new overflow-safe integer comparison functions. 2024-02-16 14:05:36 -06:00
isn
jsonb_plperl
jsonb_plpython
lo
ltree Add hash support functions and hash opclass for contrib/ltree. 2024-03-21 18:27:49 -04:00
ltree_plpython
oid2name
pageinspect Stabilize test of BRIN parallel create 2024-04-17 16:14:47 +02:00
passwordcheck
pg_buffercache Add pg_buffercache_evict() function for testing. 2024-04-08 16:23:40 +12:00
pg_freespacemap
pg_prewarm Revise GUC names quoting in messages again 2024-05-17 11:44:26 +02:00
pg_stat_statements Revise GUC names quoting in messages again 2024-05-17 11:44:26 +02:00
pg_surgery
pg_trgm Use new overflow-safe integer comparison functions. 2024-02-16 14:05:36 -06:00
pg_visibility Avoid edge case in pg_visibility test with small shared_buffers 2024-03-25 20:19:43 -07:00
pg_walinspect
pgcrypto
pgrowlocks
pgstattuple
postgres_fdw Make postgres_fdw request remote time zone 'GMT' not 'UTC'. 2024-04-21 13:46:20 -04:00
seg
sepgsql Revise GUC names quoting in messages again 2024-05-17 11:44:26 +02:00
spi
sslinfo Revert "Add notBefore and notAfter to SSL cert info display" 2024-03-22 22:58:41 +01:00
start-scripts
tablefunc Make contrib/tablefunc crosstab() also check typmod 2024-03-09 17:32:32 -05:00
tcn
test_decoding Revise GUC names quoting in messages again 2024-05-17 11:44:26 +02:00
tsm_system_rows
tsm_system_time
unaccent
uuid-ossp Make the order of the header file includes consistent 2024-03-13 15:07:00 +01:00
vacuumlo
xml2
contrib-global.mk
Makefile Remove the adminpack contrib extension 2024-03-04 12:39:22 +01:00
meson.build Remove the adminpack contrib extension 2024-03-04 12:39:22 +01:00
README

The PostgreSQL contrib tree
---------------------------

This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly
because they address a limited audience or are too experimental to be
part of the main source tree.  This does not preclude their
usefulness.

User documentation for each module appears in the main SGML
documentation.

When building from the source distribution, these modules are not
built automatically, unless you build the "world" target.  You can
also build and install them all by running "make all" and "make
install" in this directory; or to build and install just one selected
module, do the same in that module's subdirectory.

Some directories supply new user-defined functions, operators, or
types.  To make use of one of these modules, after you have installed
the code you need to register the new SQL objects in the database
system by executing a CREATE EXTENSION command.  In a fresh database,
you can simply do

    CREATE EXTENSION module_name;

See the PostgreSQL documentation for more information about this
procedure.