Re: BUG #16162: create index using gist_trgm_ops leads to panic

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, kunert(at)cms(dot)hu-berlin(dot)de, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16162: create index using gist_trgm_ops leads to panic
Date: 2019-12-16 19:00:00
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

Hello Heikki,
16.12.2019 15:02, Heikki Linnakangas wrote:
> I added the "stack-downlinkoffnum = InvalidOffsetNumber" to the first
> call on Friday. But the second call needs the same treatment, because
> it's possible that we reuse the same stack on a later call to
> gistfinishsplit(), if a grandchild page is split twice, for the same
> leaf insert. I feel pretty dumb, because I looked at that second call
> on Friday too, thinking if it also needs to reset 'downlinkoffnum',
> but somehow I concluded it does not. Clearly it does, as this test
> case demonstrates.
> Fix committed. Thanks again for the report!
I can confirm that now the issue is gone.
Thank you!

Best regards,

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2019-12-16 19:19:11 Re: Missing locales prevent autovacuum
Previous Message PG Bug reporting form 2019-12-16 18:22:33 BUG #16168: Full text search parser prefers "file" over "asciiword"