From 97460b7db5a692e5d8a1f0d49a77cf60d915be8b Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sat, 15 Jun 2002 22:15:03 +0000
Subject: [PATCH] Ooops, fix busted markup.

---
 doc/src/sgml/syntax.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml
index 9107f2d1a4..5be7ed4cc6 100644
--- a/doc/src/sgml/syntax.sgml
+++ b/doc/src/sgml/syntax.sgml
@@ -1471,11 +1471,11 @@ SELECT somefunc() OR true;
     be used.  For example, this is an untrustworthy way of trying to
     avoid division by zero in a WHERE clause:
 <programlisting>
-SELECT ... WHERE x <> 0 AND y/x > 1.5;
+SELECT ... WHERE x &lt;&gt; 0 AND y/x &gt; 1.5;
 </programlisting>
     but this is safe:
 <programlisting>
-SELECT ... WHERE CASE WHEN x <> 0 THEN y/x > 1.5 ELSE false END;
+SELECT ... WHERE CASE WHEN x &lt;&gt; 0 THEN y/x &gt; 1.5 ELSE false END;
 </programlisting>
     A CASE construct used in this fashion will defeat optimization attempts,
     so it should only be done when necessary.
-- 
2.39.5