Hi!
In Postgres 9.1.2 script below produces proper results:
1.34
5.56
In Postgres 11 it produces wrong results:
null
null
How to make it also to work in newer versions on Postgres ?
create temp table t(x xml, nsa text[][]) on commit drop;
insert into t values(
'
http://www.w3.org/2001/XML
Hi
ne 17. 3. 2019 v 12:11 odesílatel Andrus napsal:
> Hi!
>
> In Postgres 9.1.2 script below produces proper results:
>
> 1.34
> 5.56
>
> In Postgres 11 it produces wrong results:
>
> null
> null
>
> How to make it also to work in newer versions on Postgres ?
>
> create temp table t(x xml, nsa t
ne 17. 3. 2019 v 14:49 odesílatel Pavel Stehule
napsal:
> Hi
>
> ne 17. 3. 2019 v 12:11 odesílatel Andrus napsal:
>
>> Hi!
>>
>> In Postgres 9.1.2 script below produces proper results:
>>
>> 1.34
>> 5.56
>>
>> In Postgres 11 it produces wrong results:
>>
>> null
>> null
>>
>> How to make it also
Andrus schrieb am 17.03.2019 um 08:36:
In Postgres 9.1.2 script below produces proper results:
1.34
5.56
create temp table t(x xml, nsa text[][]) on commit drop;
insert into t values(
'
http://www.w3.org/2001/XMLSchema-instance";
xmlns="urn:iso:std:iso:20022:tech:xsd:camt.053.001.02">
Hi
>This variant is working
>postgres=# SELECT
>(xpath('/ns:Ntry/ns:Amt/text()', x,nsa))[1]::text::numeric AS tasusumma
>FROM (
>SELECT unnest(xpath('/ns:Document/ns:BkToCstmrStmt/ns:Stmt/ns:Ntry',
>x,nsa)) as x,
>nsa
>FROM t
>) Ntry
>;
>But I have n
Many of us have faced character encoding issues because we are not in control
of our input sources and made the common assumption that UTF-8 covers
everything.
In my lab, as an example, some of our social media posts have included ZawGyi
Burmese character sets rather than Unicode Burmese. (Bec
ne 17. 3. 2019 v 15:19 odesílatel Andrus napsal:
> Hi!
>
> >You can use XMLTABLE function
> >select xmltable.*
> > from t,
> > lateral
> > xmltable(xmlnamespaces('urn:iso:std:iso:20022:tech:xsd:camt.053.001.02'
> as
> > ns),
> >
> > '/ns:Document/ns:BkToCstmrStmt/ns:Stmt/ns:Ntry/.' pass
ne 17. 3. 2019 v 15:11 odesílatel Andrus napsal:
> Hi
>
> >This variant is working
> >postgres=# SELECT
> >(xpath('/ns:Ntry/ns:Amt/text()', x,nsa))[1]::text::numeric AS
> tasusumma
> >FROM (
> >SELECT
> unnest(xpath('/ns:Document/ns:BkToCstmrStmt/ns:Stmt/ns:Ntry',
> >x,nsa)) as x
"Andrus" writes:
>> But I have not a idea, why old code doesn't work. It is little bit strange
>> so it worked without namespace before Amt tag.
> In 9.1.5 without namespaces
> (xpath('Amt/text()', x,nsa))[1]::text::numeric AS tasusumma
> works.
> How to make it work in both versions?
I'm har
Hi!
You can use XMLTABLE function
select xmltable.*
from t,
lateral
xmltable(xmlnamespaces('urn:iso:std:iso:20022:tech:xsd:camt.053.001.02' as
ns),
'/ns:Document/ns:BkToCstmrStmt/ns:Stmt/ns:Ntry/.' passing t.x
columns tasusumma numeric path 'ns:Amt')
We aren't sure whether to use software MDRaid or a MegaRAID card.
We're buying some new Postgres servers with
2 x 240GB Intel SSD S4610 (RAID1 : system)
4 x 960GB Intel SSD S4610 (RAID10 : db)
We'll be using Postgres 11 on Debian.
The MegaRAID 9271-8i with flash cache protection is ava
Greetings,
* Martín Fernández (fmarti...@gmail.com) wrote:
> I've wrote a couple of questions around pg_upgrade and updating standbys
> using rsync last week. We were able to successfully upgrade half of our
> cluster (the other half was kept for failover) from pg92 with postgis 1.5.8
> to pg10
12 matches
Mail list logo