@@ -1303,34 +1303,6 @@ include $(PGXS)
13031303 </listitem>
13041304 </varlistentry>
13051305
1306- <varlistentry>
1307- <term><varname>ISOLATION</varname></term>
1308- <listitem>
1309- <para>
1310- list of isolation test cases, see below for more details
1311- </para>
1312- </listitem>
1313- </varlistentry>
1314-
1315- <varlistentry>
1316- <term><varname>ISOLATION_OPTS</varname></term>
1317- <listitem>
1318- <para>
1319- additional switches to pass to
1320- <application>pg_isolation_regress</application>
1321- </para>
1322- </listitem>
1323- </varlistentry>
1324-
1325- <varlistentry>
1326- <term><varname>TAP_TESTS</varname></term>
1327- <listitem>
1328- <para>
1329- switch defining if TAP tests need to be run, see below
1330- </para>
1331- </listitem>
1332- </varlistentry>
1333-
13341306 <varlistentry>
13351307 <term><varname>NO_INSTALLCHECK</varname></term>
13361308 <listitem>
@@ -1451,42 +1423,13 @@ make VPATH=/path/to/extension/source/tree install
14511423 have all expected files.
14521424 </para>
14531425
1454- <para>
1455- The scripts listed in the <varname>ISOLATION</varname> variable are used
1456- for tests stressing behavior of concurrent session with your module, which
1457- can be invoked by <literal>make installcheck</literal> after doing
1458- <literal>make install</literal>. For this to work you must have a
1459- running <productname>PostgreSQL</productname> server. The script files
1460- listed in <varname>ISOLATION</varname> must appear in a subdirectory
1461- named <literal>specs/</literal> in your extension's directory. These files
1462- must have extension <literal>.spec</literal>, which must not be included
1463- in the <varname>ISOLATION</varname> list in the makefile. For each test
1464- there should also be a file containing the expected output in a
1465- subdirectory named <literal>expected/</literal>, with the same stem and
1466- extension <literal>.out</literal>. <literal>make installcheck</literal>
1467- executes each test script, and compares the resulting output to the
1468- matching expected file. Any differences will be written to the file
1469- <literal>output_iso/regression.diffs</literal> in
1470- <command>diff -c</command> format. Note that trying to run a test that is
1471- missing its expected file will be reported as <quote>trouble</quote>, so
1472- make sure you have all expected files.
1473- </para>
1474-
1475- <para>
1476- <literal>TAP_TESTS</literal> enables the use of TAP tests. Data from each
1477- run is present in a subdirectory named <literal>tmp_check/</literal>.
1478- See also <xref linkend="regress-tap"/> for more details.
1479- </para>
1480-
14811426 <tip>
14821427 <para>
14831428 The easiest way to create the expected files is to create empty files,
14841429 then do a test run (which will of course report differences). Inspect
14851430 the actual result files found in the <literal>results/</literal>
1486- directory (for tests in <literal>REGRESS</literal>), or
1487- <literal>output_iso/results/</literal> directory (for tests in
1488- <literal>ISOLATION</literal>), then copy them to
1489- <literal>expected/</literal> if they match what you expect from the test.
1431+ directory, then copy them to <literal>expected/</literal> if they match
1432+ what you expect from the test.
14901433 </para>
14911434
14921435 </tip>
0 commit comments