Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: marcos(dot)castedo(at)anachronics(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #19816: PL/Python SD dictionary is split by input collation in 19rc1
Date: 2026-11-09 05:21:21
Message-ID: CAGRkXqSAdTj_pk3wZbjbZQU_HjB9Hj0Ybwc3J5RrFM1j7RvckA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

Thanks for reporting that.

The attached patch keeps SD in its own hash keyed by function OID and
trigger relation, as 18 did. So every cache entry of a function shares
it.

Variables set with "global" in the function body are still split, since
sharing t
hose would also mean sharing the call stack state. I left that alone, but I
can look at it if you think it matters.

This is a 19 regression, I'll add it to the open items.

Attachment Content-Type Size
v1-0001-plpython-Share-the-SD-dictionary-across-all-cache.patch application/octet-stream 8.3 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2026-11-09 05:28:37 Re: BUG #19842: pg_restore_extended_stats() rejects a faithful pg_dump of ANALYZE-produced range expression statisti
Previous Message shihao zhong 2026-11-09 05:16:41 Re: BUG #19834: eager aggregation still evaluates volatile join clauses when the volatile function is inside a SubPl