| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: brin regression test intermittent failures |
| Date: | 2015-06-04 19:29:52 |
| Message-ID: | 18709.1433446192@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> The other cases that I found involve cidrcol, and seem to represent
> an actual bug in the brin planning logic, ie failure to disregard a
> no-op cast. I'll look closer.
I leapt to the wrong conclusion on that one. The reason for failure to
match to an index column had nothing to do with the extra cast, and
everything to do with the fact that there was no such index column.
I think we're probably good now, though it'd be wise to keep an eye on
chipmunk for awhile to verify that it doesn't see the problem anymore.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-06-04 19:37:09 | Re: brin regression test intermittent failures |
| Previous Message | Alvaro Herrera | 2015-06-04 19:16:15 | Re: Further issues with jsonb semantics, documentation |