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

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation.
Date: 2013-03-21 16:14:21
Message-ID: 514B31DD.2050401@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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 sure the server is running with fresh binaries? If it
still fails, could you try to get a stack trace or something?

- Heikki

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Kevin Grittner 2013-03-21 18:15:59 Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation.
Previous Message Kevin Grittner 2013-03-21 15:37:11 pgsql: Eliminate trivial whitespace inconsistency in docs sample code.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-03-21 18:09:57 Re: sql_drop Event Triggerg
Previous Message Kevin Grittner 2013-03-21 15:20:11 Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation.