Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation. - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation.
Date
Msg-id 1363889759.76199.YahooMailNeo@web162904.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation.  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation.  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
Heikki Linnakangas <hlinnakangas@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 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.

Sorry for the noise.

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: sql_drop Event Triggerg
Next
From: Robert Haas
Date:
Subject: Re: Strange Windows problem, lock_timeout test request