Re: Crash in gist insertion on pathological box data - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Crash in gist insertion on pathological box data
Date
Msg-id 22855.1238702729@sss.pgh.pa.us
Whole thread Raw
In response to Re: Crash in gist insertion on pathological box data  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> I think that not only does there need to be another IS_BADRATIO check,
> but also there needs to be some sort of backstop in gistSplit or
> gistUserPicksplit to either recover or (as a last resort) error out
> cleanly rather than crash the entire db in cases that would result in
> infinite recursion.

+1.  This is not just a problem in one picksplit method, it's a generic
hazard for all of them.  The core code should be defending against a
pathological split.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [GENERAL] string_to_array with empty input
Next
From: Robert Haas
Date:
Subject: Re: [pgsql-www] Mentors needed urgently for SoC & PostgreSQL Student Internships