Re: Correction: 17.11/18.6 slot_getsomeattrs_int crash is not a d260d7d backpatch gap; request for triage direction

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: ssye1697 <ssye1697(at)agent(dot)qq(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Correction: 17.11/18.6 slot_getsomeattrs_int crash is not a d260d7d backpatch gap; request for triage direction
Date: 2026-11-09 04:41:40
Message-ID: CAGRkXqROF-iLtGYZ7jefJi==QqpnGgy5S5+5qHhfgrqFc21VvA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

> Crash rate tracks buffer churn in a controlled run on one instance
> (same data, same query mix, same 12 concurrent read-only sessions,
> one parameter changed):
> shared_buffers 128 MB -> 5 crashes / 2880 queries
> shared_buffers 4 GB -> 0 crashes / 2400 queries
> and on the production instance, 9600 read-only queries at 4 GB gave
> 0 crashes. At shared_buffers = 8 GB we see none at all.

Can you provide your query to help us understand this case?

Thanks,

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message shihao zhong 2026-11-09 04:57:20 Re: BUG #19843: decode(..., 'base64url') returns an extra byte for "ab="
Previous Message Tender Wang 2026-11-09 04:41:39 Re: BUG #19804: "variable not found in subplan target list", DISTINCT agg over Gather`