1 files changed, 1 insertions, 64 deletions
diff --git a/src/backend/utils/adt/bool.c b/src/backend/utils/adt/bool.c
index 4ba234c62c6..ce7967c5b86 100644
--- a/src/backend/utils/adt/bool.c
+++ b/src/backend/utils/adt/bool.c
@@ -8,7 +8,7 @@
  *
  *
  * IDENTIFICATION
- *	  $PostgreSQL: pgsql/src/backend/utils/adt/bool.c,v 1.43 2008/03/25 22:42:43 tgl Exp $
+ *	  $PostgreSQL: pgsql/src/backend/utils/adt/bool.c,v 1.44 2008/10/05 17:33:16 petere Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -222,69 +222,6 @@ boolge(PG_FUNCTION_ARGS)
 }
 
 /*
- * Per SQL92, istrue() and isfalse() should return false, not NULL,
- * when presented a NULL input (since NULL is our implementation of
- * UNKNOWN).  Conversely isnottrue() and isnotfalse() should return true.
- * Therefore, these routines are all declared not-strict in pg_proc
- * and must do their own checking for null inputs.
- *
- * Note we don't need isunknown() and isnotunknown() functions, since
- * nullvalue() and nonnullvalue() will serve.
- */
-
-Datum
-istrue(PG_FUNCTION_ARGS)
-{
-	bool		b;
-
-	if (PG_ARGISNULL(0))
-		PG_RETURN_BOOL(false);
-
-	b = PG_GETARG_BOOL(0);
-
-	PG_RETURN_BOOL(b);
-}
-
-Datum
-isfalse(PG_FUNCTION_ARGS)
-{
-	bool		b;
-
-	if (PG_ARGISNULL(0))
-		PG_RETURN_BOOL(false);
-
-	b = PG_GETARG_BOOL(0);
-
-	PG_RETURN_BOOL(!b);
-}
-
-Datum
-isnottrue(PG_FUNCTION_ARGS)
-{
-	bool		b;
-
-	if (PG_ARGISNULL(0))
-		PG_RETURN_BOOL(true);
-
-	b = PG_GETARG_BOOL(0);
-
-	PG_RETURN_BOOL(!b);
-}
-
-Datum
-isnotfalse(PG_FUNCTION_ARGS)
-{
-	bool		b;
-
-	if (PG_ARGISNULL(0))
-		PG_RETURN_BOOL(true);
-
-	b = PG_GETARG_BOOL(0);
-
-	PG_RETURN_BOOL(b);
-}
-
-/*
  * boolean-and and boolean-or aggregates.
  */