|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>|
|Subject:||Re: BUG #16162: create index using gist_trgm_ops leads to panic|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
> This only happens on some runs (in my case the CREATE INDEX passed 8x
> without any issue and failed on 9th iteration), so there has to be some
> random element affecting this.
As far as that goes, gistchoose() intentionally makes random choices
when two insertion paths seem equally good. So failing only sometimes
isn't very surprising.
> so maybe the GIST stack is stale, not updated, or something like that. I
> think I've seen an issue mentioning that recently ... yep, found it .
> And I see Tom came to about the same conclusion, pointing to the same
> place in gistfinishsplit. It's only a couple days old, I don't think
> I've seen any proposed fixes yet.
Good that we seem to have just one bug there not two :-(. I've not
looked any further than my previous message, though.
I wonder if this could be a recently-introduced bug? I do not
recall seeing complaints like this before v12.
regards, tom lane
|Next Message||PG Bug reporting form||2019-12-12 15:20:47||BUG #16163: Seq scan through all the partitions on a partitioned table when joined small, dictionary table.|
|Previous Message||Alvaro Herrera||2019-12-12 12:52:29||Re: BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting|