Horton

Re: patch: function xmltable

Pavel Stehule <pavel.stehule@gmail.com>

View thread View on postgr.es
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Craig Ringer <craig@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2017-02-20T18:12:55Z
Lists: pgsql-hackers

Attachments

Hi

2017-02-16 6:38 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:

> Hi
>
>
>> please see attached patch
>>
>> * enhanced regress tests
>> * clean memory context work
>>
>
> new update
>
> fix a bug in string compare
> fix some typo and obsolete comments
>
> Regards
>

some minor but interesting fix.

I found so some xml values imported via recv function can have
inconsistency between header encoding and used encoding. Internally the
header encoding is removed - see xml_out function.

So now, when I have to prepare data for libxml2, I don't do direct cast,
but I use xml_out_internal instead. Maybe this technique should be used
elsewhere? Same issue I see on xpath function.

Solved issue is not too often probably - the some different encoding than
utf8 should be used in XML document and XML document should be loaded with
recv function.

Regards

Pavel



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

Commits

  1. Support XMLTABLE query expression

  2. Create <sect3> in the functions-xml section

  3. Improve handling of "UPDATE ... SET (column_list) = row_constructor".

  4. Add xmlexists function