Re: [7.0beta3] Bug in initdb

> Sorry but I couldn't find the bug-template file as indicated in
> item 1.13 of the FAQ.
>
> I came across a minor bug in PostgreSQL 7.0beta3 on my NetBSD 1.4
> system when running initdb (compile was smooth):
>
> initdb: data path must be specified as an absolute path
>
> It seems the ! if this test takes precedence over the pipe:
>
> if echo "$PGDATA" | grep -v '^/' > /dev/null 2>&1
> then
>     echo "$CMDNAME: data path must be specified as an absolute path"
> fi
>
> This patch solves the problem:
>
> --- initdb.orig       Sun Apr  2 22:32:40 2000
> +++ initdb      Sun Apr  2 22:28:21 2000
> @@ -282,7 +282,7 @@
>  # The data path must be absolute, because the backend doesn't like
>  # '.' and '..' stuff. (Should perhaps be fixed there.)
>
> -if ! echo "$PGDATA" | grep '^/' > /dev/null 2>&1
> +if echo "$PGDATA" | grep -v '^/' > /dev/null 2>&1
>  then
>      echo "$CMDNAME: data path must be specified as an absolute path"
>  fi

Well the good news is it seems someone else fixed it.  Can you try 7.0
current and see if that is better.  Thanks.

--
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026