summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNoah Misch <noah@leadboat.com>2017-11-11 13:07:46 -0800
committerNoah Misch <noah@leadboat.com>2017-11-11 13:07:55 -0800
commite48fb50d8b4868de821f09f19985e35dc5f41c44 (patch)
tree09a2a0064ca3f4d76c78616f81110788927d5e76
parent2f4061aff504049767602927e69c85b5b4621273 (diff)
Fix previous commit's test, for non-UTF8 databases with non-XML builds.
To ensure stable output, catch one more configuration-specific error. Back-patch to 9.3, like the commit that added the test.
-rw-r--r--src/test/regress/expected/xml.out16
-rw-r--r--src/test/regress/expected/xml_1.out20
-rw-r--r--src/test/regress/expected/xml_2.out16
-rw-r--r--src/test/regress/sql/xml.sql16
4 files changed, 40 insertions, 28 deletions
diff --git a/src/test/regress/expected/xml.out b/src/test/regress/expected/xml.out
index 39d94eaf561..1b8f822b187 100644
--- a/src/test/regress/expected/xml.out
+++ b/src/test/regress/expected/xml.out
@@ -660,11 +660,12 @@ DECLARE
degree_symbol text;
res xml[];
BEGIN
- -- Per the documentation, xpath() doesn't work on non-ASCII data when
- -- the server encoding is not UTF8. The EXCEPTION block below,
- -- currently dead code, will be relevant if we remove this limitation.
+ -- Per the documentation, except when the server encoding is UTF8, xpath()
+ -- may not work on non-ASCII data. The untranslatable_character and
+ -- undefined_function traps below, currently dead code, will become relevant
+ -- if we remove this limitation.
IF current_setting('server_encoding') <> 'UTF8' THEN
- RAISE LOG 'skip: encoding % unsupported for xml',
+ RAISE LOG 'skip: encoding % unsupported for xpath',
current_setting('server_encoding');
RETURN;
END IF;
@@ -679,9 +680,12 @@ BEGIN
END IF;
EXCEPTION
-- character with byte sequence 0xc2 0xb0 in encoding "UTF8" has no equivalent in encoding "LATIN8"
- WHEN untranslatable_character THEN RAISE LOG 'skip: %', SQLERRM;
+ WHEN untranslatable_character
-- default conversion function for encoding "UTF8" to "MULE_INTERNAL" does not exist
- WHEN undefined_function THEN RAISE LOG 'skip: %', SQLERRM;
+ OR undefined_function
+ -- unsupported XML feature
+ OR feature_not_supported THEN
+ RAISE LOG 'skip: %', SQLERRM;
END
$$;
-- Test xmlexists and xpath_exists
diff --git a/src/test/regress/expected/xml_1.out b/src/test/regress/expected/xml_1.out
index ab136376c28..0098d106ea6 100644
--- a/src/test/regress/expected/xml_1.out
+++ b/src/test/regress/expected/xml_1.out
@@ -571,11 +571,12 @@ DECLARE
degree_symbol text;
res xml[];
BEGIN
- -- Per the documentation, xpath() doesn't work on non-ASCII data when
- -- the server encoding is not UTF8. The EXCEPTION block below,
- -- currently dead code, will be relevant if we remove this limitation.
+ -- Per the documentation, except when the server encoding is UTF8, xpath()
+ -- may not work on non-ASCII data. The untranslatable_character and
+ -- undefined_function traps below, currently dead code, will become relevant
+ -- if we remove this limitation.
IF current_setting('server_encoding') <> 'UTF8' THEN
- RAISE LOG 'skip: encoding % unsupported for xml',
+ RAISE LOG 'skip: encoding % unsupported for xpath',
current_setting('server_encoding');
RETURN;
END IF;
@@ -590,15 +591,14 @@ BEGIN
END IF;
EXCEPTION
-- character with byte sequence 0xc2 0xb0 in encoding "UTF8" has no equivalent in encoding "LATIN8"
- WHEN untranslatable_character THEN RAISE LOG 'skip: %', SQLERRM;
+ WHEN untranslatable_character
-- default conversion function for encoding "UTF8" to "MULE_INTERNAL" does not exist
- WHEN undefined_function THEN RAISE LOG 'skip: %', SQLERRM;
+ OR undefined_function
+ -- unsupported XML feature
+ OR feature_not_supported THEN
+ RAISE LOG 'skip: %', SQLERRM;
END
$$;
-ERROR: unsupported XML feature
-DETAIL: This functionality requires the server to be built with libxml support.
-HINT: You need to rebuild PostgreSQL using --with-libxml.
-CONTEXT: PL/pgSQL function inline_code_block line 17 at assignment
-- Test xmlexists and xpath_exists
SELECT xmlexists('//town[text() = ''Toronto'']' PASSING BY REF '<towns><town>Bidford-on-Avon</town><town>Cwmbran</town><town>Bristol</town></towns>');
ERROR: unsupported XML feature
diff --git a/src/test/regress/expected/xml_2.out b/src/test/regress/expected/xml_2.out
index eb1fd92b3e1..ea68d975d9c 100644
--- a/src/test/regress/expected/xml_2.out
+++ b/src/test/regress/expected/xml_2.out
@@ -642,11 +642,12 @@ DECLARE
degree_symbol text;
res xml[];
BEGIN
- -- Per the documentation, xpath() doesn't work on non-ASCII data when
- -- the server encoding is not UTF8. The EXCEPTION block below,
- -- currently dead code, will be relevant if we remove this limitation.
+ -- Per the documentation, except when the server encoding is UTF8, xpath()
+ -- may not work on non-ASCII data. The untranslatable_character and
+ -- undefined_function traps below, currently dead code, will become relevant
+ -- if we remove this limitation.
IF current_setting('server_encoding') <> 'UTF8' THEN
- RAISE LOG 'skip: encoding % unsupported for xml',
+ RAISE LOG 'skip: encoding % unsupported for xpath',
current_setting('server_encoding');
RETURN;
END IF;
@@ -661,9 +662,12 @@ BEGIN
END IF;
EXCEPTION
-- character with byte sequence 0xc2 0xb0 in encoding "UTF8" has no equivalent in encoding "LATIN8"
- WHEN untranslatable_character THEN RAISE LOG 'skip: %', SQLERRM;
+ WHEN untranslatable_character
-- default conversion function for encoding "UTF8" to "MULE_INTERNAL" does not exist
- WHEN undefined_function THEN RAISE LOG 'skip: %', SQLERRM;
+ OR undefined_function
+ -- unsupported XML feature
+ OR feature_not_supported THEN
+ RAISE LOG 'skip: %', SQLERRM;
END
$$;
-- Test xmlexists and xpath_exists
diff --git a/src/test/regress/sql/xml.sql b/src/test/regress/sql/xml.sql
index 62a4736275f..249f7b7d882 100644
--- a/src/test/regress/sql/xml.sql
+++ b/src/test/regress/sql/xml.sql
@@ -193,11 +193,12 @@ DECLARE
degree_symbol text;
res xml[];
BEGIN
- -- Per the documentation, xpath() doesn't work on non-ASCII data when
- -- the server encoding is not UTF8. The EXCEPTION block below,
- -- currently dead code, will be relevant if we remove this limitation.
+ -- Per the documentation, except when the server encoding is UTF8, xpath()
+ -- may not work on non-ASCII data. The untranslatable_character and
+ -- undefined_function traps below, currently dead code, will become relevant
+ -- if we remove this limitation.
IF current_setting('server_encoding') <> 'UTF8' THEN
- RAISE LOG 'skip: encoding % unsupported for xml',
+ RAISE LOG 'skip: encoding % unsupported for xpath',
current_setting('server_encoding');
RETURN;
END IF;
@@ -212,9 +213,12 @@ BEGIN
END IF;
EXCEPTION
-- character with byte sequence 0xc2 0xb0 in encoding "UTF8" has no equivalent in encoding "LATIN8"
- WHEN untranslatable_character THEN RAISE LOG 'skip: %', SQLERRM;
+ WHEN untranslatable_character
-- default conversion function for encoding "UTF8" to "MULE_INTERNAL" does not exist
- WHEN undefined_function THEN RAISE LOG 'skip: %', SQLERRM;
+ OR undefined_function
+ -- unsupported XML feature
+ OR feature_not_supported THEN
+ RAISE LOG 'skip: %', SQLERRM;
END
$$;