Re: [HACKERS] [COMMITTERS] pgsql: Fix element @ range cost estimation.

2013-03-21 Thread Kevin Grittner
Heikki Linnakangas heikki.linnakan...@iki.fi wrote: Fix element @ range cost estimation. The statistics-based cost estimation patch for range types broke that, by incorrectly assuming that the left operand of all range oeprators is a range. That lead to a type x is not a range type error.

Re: [HACKERS] [COMMITTERS] pgsql: Fix element @ range cost estimation.

2013-03-21 Thread Heikki Linnakangas
On 21.03.2013 17:20, Kevin Grittner wrote: Something is still wrong. When I run `make check-world` everything passes, but `make installcheck-world` on a fresh initdb with default configuration yields this: Huh, that's strange. It works for me, and the build farm is happy. I must ask: are you

Re: [HACKERS] [COMMITTERS] pgsql: Fix element @ range cost estimation.

2013-03-21 Thread Kevin Grittner
Heikki Linnakangas hlinnakan...@vmware.com wrote: Huh, that's strange. It works for me, and the build farm is happy. I must ask: are you sure the server is running with fresh binaries? If it still fails, could you try to get a stack trace or something? Hmm.  Just to be sure I used

Re: [HACKERS] [COMMITTERS] pgsql: Fix element @ range cost estimation.

2013-03-21 Thread Dimitri Fontaine
Kevin Grittner kgri...@ymail.com writes: Hmm.  Just to be sure I used maintainer-clean and another initdb and now I don't see it.  If I see it again I'll get a stack trace, but for now it's not throwing the error. It happened to me way too many times to have to do maintainer-clean for reasons