From: | "Mike Miller" <temp6453(at)hotmail(dot)com> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: INIT DB FAILURE |
Date: | 2001-01-16 21:36:29 |
Message-ID: | F348Ua8d9Ee4zadTMVw00000091@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
GNU sed version 3.02.80
>From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>To: "Mike Miller" <temp6453(at)hotmail(dot)com>
>CC: pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
>Subject: Re: Re: INIT DB FAILURE
>Date: Tue, 16 Jan 2001 16:21:31 -0500
>
>"Mike Miller" <temp6453(at)hotmail(dot)com> writes:
> > mv global.bki global.bki.old; mv template1.bki template1.bki.old
> > cat global.bki.old | sed s/" ame"/" name"/ > global.bki
> > cat template1.bki.old | sed s/" ame"/" name"/ > global.bki
>
> > Solution is pretty simple actually (did figure this one out). I did
>find
> > other people complaining about this, but no solutions. But I just did
>the
> > install on an older slackware system and diffed the bki files to find
>some
> > as 'ame' and others as 'name' - so I used the lines above and managed to
>get
> > it to work just fine.
>
>OK, so the breakage is not in the bootstrap parser but in the generation
>of the .bki files. This is done by the shell script
>src/backend/catalog/genbki.sh, and in looking it over, I notice with
>suspicion the step
>
>sed -e "s/;[ ]*$//g" \
> -e "s/^[ ]*//" \
> -e "s/[ ]Oid/\ oid/g" \
> -e "s/[ ]NameData/\ name/g" \
> -e "s/^Oid/oid/g" \
> -e "s/^NameData/\name/g" \
> -e "s/(NameData/(name/g" \
> -e "s/(Oid/(oid/g" \
> -e "s/NAMEDATALEN/$NAMEDATALEN/g" \
> -e "s/INDEX_MAX_KEYS\*2/$INDEXMAXKEYS2/g" \
> -e "s/INDEX_MAX_KEYS\*4/$INDEXMAXKEYS4/g" \
> -e "s/INDEX_MAX_KEYS/$INDEXMAXKEYS/g" \
> -e "s/FUNC_MAX_ARGS\*2/$INDEXMAXKEYS2/g" \
> -e "s/FUNC_MAX_ARGS\*4/$INDEXMAXKEYS4/g" \
> -e "s/FUNC_MAX_ARGS/$INDEXMAXKEYS/g" \
>| $AWK '
>
>In particular that "\name" looks pretty bogus. Would you try removing
>that backslash and see if the script works then? I'll betcha that some
>versions of sed convert the \n to a newline ...
>
>BTW, what version of sed do you have, exactly?
>
> regards, tom lane
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Shraibman | 2001-01-16 21:53:24 | postgres 7.0.3 core dumps |
Previous Message | Tom Lane | 2001-01-16 21:21:31 | Re: Re: INIT DB FAILURE |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-16 22:27:04 | DeadLockCheck is buggy |
Previous Message | Mikheev, Vadim | 2001-01-16 21:22:26 | RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea |