Commit 6a04c571 authored by Bruce Momjian's avatar Bruce Momjian

Change "IN/NOT IN" to "IN / NOT IN" for clarity, both branches.

parent 1acc6578
...@@ -10,7 +10,7 @@ ...@@ -10,7 +10,7 @@
Major changes in this release: Major changes in this release:
IN/NOT IN subqueries are now much more efficient IN / NOT IN subqueries are now much more efficient
In previous releases, IN/NOT IN subqueries were joined to the In previous releases, IN/NOT IN subqueries were joined to the
upper query by sequentially scanning the subquery looking for a upper query by sequentially scanning the subquery looking for a
match. The 7.4 code uses the same sophisticated techniques used match. The 7.4 code uses the same sophisticated techniques used
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.243 2003/11/16 03:23:48 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.244 2003/11/17 04:50:56 momjian Exp $
--> -->
<appendix id="release"> <appendix id="release">
...@@ -22,7 +22,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.243 2003/11/16 03:23:48 tg ...@@ -22,7 +22,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.243 2003/11/16 03:23:48 tg
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term> <term>
<literal>IN</literal>/<literal>NOT IN</literal> subqueries are <literal>IN</literal> / <literal>NOT IN</literal> subqueries are
now much more efficient now much more efficient
</term> </term>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment