Re: bugfix: xpath encoding issue

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bugfix: xpath encoding issue
Date: 2017-04-13 17:35:50
Message-ID: CAFj8pRBcAeNU-bya3DrSqcnHGVb5pQFVTtAO7DPEvB9Wg2_tsA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2017-04-13 17:19 GMT+02:00 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:

> Pavel Stehule wrote:
> > Hi
> >
> > When I tested XMLTABLE function I found a bug of XPATH function -
> > xpath_internal
> >
> > There xmltype is not correctly encoded to xmlChar due possible invalid
> > encoding info in header. It is possible when XML was loaded with recv
> > function and has not UTF8 encoding.
>
> Hmm ... is it possible to create a test that verifies this? I suppose
> we could have a non-utf8 value as bytea.
>

I have not any idea. The problem is in utf8 encoded xml with bad header.
There is dependency to database encoding and supported locales.

Maybe I can simulate it with cast without function from bytea to xml - but
it looks more than little bit dirty

Regards

Pavel

>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2017-04-13 17:46:57 Re: Undefined psql variables
Previous Message Fujii Masao 2017-04-13 17:31:32 Re: tablesync patch broke the assumption that logical rep depends on?