| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation. |
| Date: | 2013-03-21 18:15:59 |
| Message-ID: | 1363889759.76199.YahooMailNeo@web162904.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-03-21 20:27:25 | Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation. |
| Previous Message | Heikki Linnakangas | 2013-03-21 16:14:21 | Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-03-21 18:24:10 | Re: Strange Windows problem, lock_timeout test request |
| Previous Message | Robert Haas | 2013-03-21 18:09:57 | Re: sql_drop Event Triggerg |