Re: BUG #19486: Regression in SQL-language functions using XML values and IS DOCUMENT
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: PetSerAl <petseral@gmail.com>
Cc: a.prototype7@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2026-05-25T21:23:27Z
Lists: pgsql-bugs
PetSerAl <petseral@gmail.com> writes:
>> CREATE OR REPLACE FUNCTION xml_to_text_no_inline(pXml xml) RETURNS text
>> LANGUAGE sql
>> IMMUTABLE
>> SET search_path = pg_catalog
>> AS $$
>> SELECT CASE WHEN pXml IS DOCUMENT
>> THEN (xpath('/*/text()', pXml))[1]::text
>> ELSE pXml::text
>> END;
>> $$;
> There is bug in that function. Expectation, that `xpath('/*/text()',
> pXml)` will be evaluate only after successful `pXml IS DOCUMENT`
> check, is not supported by documentation.
Yeah, CASE is not strong enough to prevent constant-folding in this
context. You could try something like
create or replace function xml_to_text(pXml xml) returns text
as $$
select
coalesce(
(xpath('/*/text()',
case when pXml is document then pXml else null end))[1],
pXml
)::text;
$$ language sql immutable;
This works because xpath() is strict so it won't try to do anything
with a NULL input, just return NULL; and then the COALESCE() serves
the purpose of injecting pXml when that happens.
regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
postgres_fdw: Fix deparsing of remote column names in stats import.
- 5107398e6d5e 19 (unreleased) cited
-
pgbench: fix verbose error message corruption with multiple threads
- 98dd6c204696 18 (unreleased) cited
-
Add GiST and btree sortsupport routines for range types
- e9e7b66044c9 18.0 cited