| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | teodor(at)sigaev(dot)ru (Teodor Sigaev), pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Crash in gist insertion on pathological box data |
| Date: | 2009-04-02 20:05:29 |
| Message-ID: | 22855.1238702729@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-04-02 20:07:04 | Re: [HACKERS] Mentors needed urgently for SoC & PostgreSQL Student Internships |
| Previous Message | Robert Haas | 2009-04-02 20:01:29 | Re: [HACKERS] string_to_array with empty input |