Re: Recently-introduced segfault in initdb?

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Recently-introduced segfault in initdb?
Date: 2018-03-18 09:57:39
Message-ID: 20180318095739.it5p72an757pj3um@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Isaac Morland wrote:
> OK, I must have done something wrong with the bisect the first time. Now
> I'm getting the following as the problem commit:
>
> fd1a421fe66173fb9b85d3fe150afde8e812cbe4 is the first bad commit

Did you run "make distclean" before git-pulling? If not, maybe what you
have is an incomplete rebuild after the code update. Unless you have
--enable-depend in your configure line ...?

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2018-03-18 12:24:30 Re: MCV lists for highly skewed distributions
Previous Message Pavan Deolasee 2018-03-18 06:01:58 Re: [HACKERS] MERGE SQL Statement for PG11