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

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

Hi Tom,

I have a proposal. SD stays with the cache entry, and plpython leaves
the input collation out of its cache key.

The reason is that an entry should only split on what changes the
compiled code. The trigger relation does, and so would the actual
argument types once plpython has polymorphic arguments. The collation
does not, since plpython never uses it.

If that sounds right, I'll send a v2.

Thanks,
Shihao

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message shihao zhong 2026-11-09 23:09:19 Re: BUG #19849: queries fail after ANALYZE with expression stats on arrays
Previous Message Masahiko Sawada 2026-11-09 22:43:34 Re: BUG #19702: decode() accepts Base64 payload after terminal padding