PG Bug reporting form <noreply@postgresql.org> writes:
> It appears the PL/pgSQL assignment operator := fails to maintain the
> stability of a jsonb attribute reference (from a function result) during a
> self-concatenation operation, whereas a SELECT wrapper forces correct
> materialization.
Your problem is operator precedence:
> v_payload := v_payload || tj->'delta'; -- The problematic line
> v_payload := (SELECT v_payload || (tj->'delta')); --This avoids the issue.
The second formulation works because of the "extra" parentheses;
that is,
v_payload || tj->'delta'
is parsed as
(v_payload || tj)->'delta'
but what you need is
v_payload || (tj->'delta')
Yeah, this isn't super intuitive, but all our non-SQL-standard
operators have the same precedence [1], so || and -> associate
left-to-right by default.
regards, tom lane
[1] https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-PRECEDENCE
