Re: Recently-introduced segfault in initdb?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Recently-introduced segfault in initdb?
Date: 2018-03-18 16:48:47
Message-ID: 22992.1521391727@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Isaac Morland <isaac(dot)morland(at)gmail(dot)com> writes:
> Thank you, and sorry everybody for the noise. Yes, I just did a "make
> distclean" and then the build worked.

Yeah, this is something most of us have learned the hard way over
time ;-). Either use --enable-depend, or religiously do "make
distclean" before any git pull, git bisect, etc. I prefer the
latter because it avoids leaving junk files laying around, such
as .o files that should exist in one version but not another;
but if you're less annoyed by that sort of thing than I am,
--enable-depend is a good alternative.

In any case, using ccache is recommendable if your platform doesn't
already set you up to use that automatically. Also, if you choose
the "make distclean" approach, you're going to be re-running
configure a lot, so it's good to use --cache-file with that.
These together with "make -j" will get the rebuild time down to
maybe 15 seconds on modern hardware.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christos Maris 2018-03-18 17:06:09 [GSoC] Proposal Submission
Previous Message Andrey Borodin 2018-03-18 16:39:16 Re: [GSoC 2018] Proposal Draft