mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix capitalization of "Tcl"

Browse Source
This commit is contained in:
Peter Eisentraut 2023-11-14 10:44:44 +01:00
parent 43071777be
commit e7814b40d0
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/install-windows.sgml
View File

@ -205,7 +205,7 @@ $ENV{MSBFLAGS}="/m";
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term><productname>ActiveState TCL</productname></term> <term><productname>ActiveState Tcl</productname></term>
<listitem><para> <listitem><para>
Required for building <application>PL/Tcl</application> (Note: version Required for building <application>PL/Tcl</application> (Note: version
8.4 is required, the free Standard Distribution is sufficient). 8.4 is required, the free Standard Distribution is sufficient).

2
doc/src/sgml/xact.sgml
View File

@ -122,7 +122,7 @@
Subtransactions can be started explicitly using the Subtransactions can be started explicitly using the
<command>SAVEPOINT</command> command, but can also be started in <command>SAVEPOINT</command> command, but can also be started in
other ways, such as PL/pgSQL's <literal>EXCEPTION</literal> clause. other ways, such as PL/pgSQL's <literal>EXCEPTION</literal> clause.
PL/Python and PL/TCL also support explicit subtransactions. PL/Python and PL/Tcl also support explicit subtransactions.
Subtransactions can also be started from other subtransactions. Subtransactions can also be started from other subtransactions.
The top-level transaction and its child subtransactions form a The top-level transaction and its child subtransactions form a
hierarchy or tree, which is why we refer to the main transaction as hierarchy or tree, which is why we refer to the main transaction as

2
src/pl/tcl/pltcl.c
View File

@ -334,7 +334,7 @@ static void pltcl_init_tuple_store(pltcl_call_state *call_state);
/* /*
* Hack to override Tcl's builtin Notifier subsystem. This prevents the * Hack to override Tcl's builtin Notifier subsystem. This prevents the
* backend from becoming multithreaded, which breaks all sorts of things. * backend from becoming multithreaded, which breaks all sorts of things.
* That happens in the default version of Tcl_InitNotifier if the TCL library * That happens in the default version of Tcl_InitNotifier if the Tcl library
* has been compiled with multithreading support (i.e. when TCL_THREADS is * has been compiled with multithreading support (i.e. when TCL_THREADS is
* defined under Unix, and in all cases under Windows). * defined under Unix, and in all cases under Windows).
* It's okay to disable the notifier because we never enter the Tcl event loop * It's okay to disable the notifier because we never enter the Tcl event loop