Re: [HACKERS] Bad Build

I get this from initdb:

[gcope(at)mouse pgsql]$ initdb
The files belonging to this database system will be owned by user
"gcope".
This user must also own the server process.

Fixing permissions on existing directory /usr/local/src/pgsql/data... ok
creating directory /usr/local/src/pgsql/data/base... ok
creating directory /usr/local/src/pgsql/data/global... ok
creating directory /usr/local/src/pgsql/data/pg_xlog... ok
creating directory /usr/local/src/pgsql/data/pg_clog... ok
creating template1 database in /usr/local/src/pgsql/data/base/1...
/usr/bin/initdb: line 473: 1234 Broken pipe cat
"$POSTGRES_BKI"
1235 | sed -e
"s/POSTGRES/$POSTGRES_SUPERUSERNAME/g" -e "s/ENCODING/$MULTIBYTEID/g"
1236 Segmentation fault | "$PGPATH"/postgres -boot -x1
$PGSQL_OPT $BACKEND_TALK_ARG template1

initdb failed.

On Wed, 2002-03-06 at 10:39, Rod Taylor wrote:
> Current CVS of postgres is completely broken.
>
> initdb fails with SIG11 during the 'creation of template1'
>
> --debug doesn't show anything being written.
>
> Several regression tests have postmaster crashing.
>
> These appeared somewhere between 4 days ago and yesterday.
>
> I'm afraid I really don't know where to start debugging the problem.
> --
> Rod Taylor
>
> Your eyes are weary from staring at the CRT. You feel sleepy. Notice
> how restful it is to watch the cursor blink. Close your eyes. The
> opinions stated above are yours. You cannot imagine why you ever felt
> otherwise.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org