From 8e5a10d46c38976e40504456a5978caa53b77b3c Mon Sep 17 00:00:00 2001
From: Neil Conway
Date: Wed, 1 Mar 2006 06:30:32 +0000
Subject: This patch makes the error message strings throughout the backend
 more compliant with the error message style guide. In particular, errdetail
 should begin with a capital letter and end with a period, whereas errmsg
 should not. I also fixed a few related issues in passing, such as fixing the
 repeated misspelling of "lexeme" in contrib/tsearch2 (per Tom's suggestion).

---
 contrib/xml2/xpath.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'contrib/xml2/xpath.c')

diff --git a/contrib/xml2/xpath.c b/contrib/xml2/xpath.c
index b4b06a039d7..662731b5c04 100644
--- a/contrib/xml2/xpath.c
+++ b/contrib/xml2/xpath.c
@@ -600,7 +600,7 @@ pgxml_result_to_text(xmlXPathObjectPtr res,
 			break;
 
 		default:
-			elog(NOTICE, "Unsupported XQuery result: %d", res->type);
+			elog(NOTICE, "unsupported XQuery result: %d", res->type);
 			xpresstr = xmlStrdup("<unsupported/>");
 	}
 
@@ -781,8 +781,8 @@ xpath_table(PG_FUNCTION_ARGS)
 	if (spi_tupdesc->natts != 2)
 	{
 		ereport(ERROR, (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
-						errmsg("Expression returning multiple columns is not valid in parameter list"),
-						errdetail("Expected two columns in SPI result, got %d", spi_tupdesc->natts)));
+						errmsg("expression returning multiple columns is not valid in parameter list"),
+						errdetail("Expected two columns in SPI result, got %d.", spi_tupdesc->natts)));
 	}
 
 /* Setup the parser. Beware that this must happen in the same context as the
@@ -890,7 +890,7 @@ xpath_table(PG_FUNCTION_ARGS)
 								break;
 
 							default:
-								elog(NOTICE, "Unsupported XQuery result: %d", res->type);
+								elog(NOTICE, "unsupported XQuery result: %d", res->type);
 								resstr = xmlStrdup("<unsupported/>");
 						}
 
-- 
cgit v1.2.3