Re: BUG #17229: Segmentation Fault after upgrading to version 13

We've been running 13.4 since last Thursday on our test cluster and haven't seen the dump.
I would say the latest patched addressed the issue.
On a separate note, applying 13.4 on a running cluster caused some issues with;
"could not load library "/usr/pgsql-13/lib/plpgsql.so": /usr/pgsql-13/lib/plpgsql.so: undefined symbol: EnsurePortalSnapshotExists"
...just FYI....
I would considered this issue with the gist index resolved.
Thanks,Efrain J. Berdecia

On Tuesday, October 19, 2021, 07:17:26 AM EDT, Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:

On Mon, Oct 18, 2021 at 9:27 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> On Mon, Oct 18, 2021 at 11:20 AM Efrain J. Berdecia
> <ejberdecia(at)yahoo(dot)com> wrote:
> > #0  __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1852
> > #1  0x00007f42aee2488b in memcpy (__len=12, __src=0x7023c19c7, __dest=0x291967d) at /usr/include/bits/string3.h:51
> > #2  gtrgm_alloc (isalltrue=<optimized out>, siglen=siglen(at)entry=12, sign=0x7023c19c7 <Address 0x7023c19c7 out of bounds>) at trgm_gist.c:82
> > #3  0x00007f42aee25d80 in gtrgm_picksplit (fcinfo=<optimized out>) at trgm_gist.c:852
> > #4  0x00000000008afcfa in FunctionCall2Coll (flinfo=flinfo(at)entry=0x2bf9400, collation=<optimized out>, arg1=arg1(at)entry=43095272, arg2=arg2(at)entry=140737194144480) at fmgr.c:1164
> > #5  0x00000000004b2d03 in gistUserPicksplit (len=2, giststate=0x2bf75d8, itup=0x29193c8, v=0x7fffee76b2e0, attno=0, entryvec=0x29194e8, r=0x7f42aecd3668) at gistsplit.c:433
>
> Commit 911e702077 ("Implement operator class parameters") seems like
> the most likely culprit, based on a quick "git blame". Alexander?

As I can see from the bug report, the affected version is 13.1.  I
think this bug is already fixed by 48ab1fa304 in 13.2.

------
Regards,
Alexander Korotkov