Re: Recently-introduced segfault in initdb? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Recently-introduced segfault in initdb?
Date
Msg-id 20180318095739.it5p72an757pj3um@alvherre.pgsql
Whole thread Raw
In response to Re: Recently-introduced segfault in initdb?  (Isaac Morland <isaac.morland@gmail.com>)
Responses Re: Recently-introduced segfault in initdb?
List 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


pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: [HACKERS] MERGE SQL Statement for PG11
Next
From: John Naylor
Date:
Subject: Re: MCV lists for highly skewed distributions