Add a new function "pg_client_encoding" which returns the current client

side encoding name. This is necessary for client API's such as JDBC
to perform correct encoding conversions. See my email "[HACKERS]
pg_client_encoding" 10 Sep 2001.

1 files changed, 8 insertions, 1 deletions

diff --git a/src/backend/utils/mb/mbutils.c b/src/backend/utils/mb/mbutils.c
index 177cd3a1d6f..c0949a6324f 100644
--- a/src/backend/utils/mb/mbutils.c
+++ b/src/backend/utils/mb/mbutils.c
@@ -3,7 +3,7 @@
  * client encoding and server internal encoding.
  * (currently mule internal code (mic) is used)
  * Tatsuo Ishii
- * $Id: mbutils.c,v 1.23 2001/09/21 15:27:38 tgl Exp $
+ * $Id: mbutils.c,v 1.24 2001/10/12 02:08:34 ishii Exp $
  */
 #include "postgres.h"
 
@@ -471,3 +471,10 @@ getdatabaseencoding(PG_FUNCTION_ARGS)
 	Assert(DatabaseEncoding);
 	return DirectFunctionCall1(namein, CStringGetDatum(DatabaseEncoding->name));
 }
+
+Datum
+pg_client_encoding(PG_FUNCTION_ARGS)
+{
+	Assert(ClientEncoding);
+	return DirectFunctionCall1(namein, CStringGetDatum(ClientEncoding->name));
+}