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
commit fd1a421fe66173fb9b85d3fe150afde8e812cbe4
Author: Peter Eisentraut <pete...@gmx.net>
Date: Fri Mar 2 08:57:38 2018 -0500
Add prokind column, replacing proisagg and proiswindow
The new column distinguishes normal functions, procedures, aggregates,
and window functions. This replaces the existing columns proisagg and
proiswindow, and replaces the convention that procedures are indicated
by prorettype == 0. Also change prorettype to be VOIDOID for
procedures.
Reviewed-by: Tom Lane <t...@sss.pgh.pa.us>
Reviewed-by: Michael Paquier <mich...@paquier.xyz>
:040000 040000 43854d518b5fdb6b36b6cc5d1f625f75f6b1974c
96aefd013c0ccf730e69a2a3611de9ab4f12294d M doc
:040000 040000 5f0e806094bdeb8e14ddf098ec7c318f574ec548
2916aea3ab2049c0317d5edd788968c167aecfde M src
bisect run success
01:52 ijmorlan@scsmac161$
When it's not working, I get the following output from initdb:
The files belonging to this database system will be owned by user
"ijmorlan".
This user must also own the server process.
The database cluster will be initialized with locale "C".
The default text search configuration will be set to "english".
Data page checksums are enabled.
creating directory ./test/pgdata ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... TRAP:
FailedAssertion("!(!isNull)", File: "catcache.c", Line: 365)
sh: line 1: 45094 Abort trap: 6 "/usr/local/pgsql/bin/postgres"
--single -F -O -j -c search_path=pg_catalog -c exit_on_error=true template1
> /dev/null
child process exited with exit code 134
initdb: removing data directory "./test/pgdata"
I hope this is more helpful.
On 18 March 2018 at 01:08, Isaac Morland <isaac.morl...@gmail.com> wrote:
> I am trying to develop a small proof-of-concept patch for a proposal I
> have, but recently I found that initdb started segfaulting after I did a
> git pull. I used git bisect and it identified the following commit as the
> first one with the problem:
>
[....]
