Re: [HACKERS] sqgfault on initdb with current CVS - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: [HACKERS] sqgfault on initdb with current CVS
Date
Msg-id 20000307100716Q.t-ishii@sra.co.jp
Whole thread Raw
In response to sqgfault on initdb with current CVS  ("Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>)
Responses Re: [HACKERS] sqgfault on initdb with current CVS  ("Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>)
List pgsql-hackers
> Sorry about the length of this one, but I wanted to include backtrace
> info.  I've been getting a segfault when I try to setup a test version
> of the current CVS tree, to run along beside a 'production' 6.5.X server.
> 
> This is how I've configured it:
> 
> wallace$./configure --prefix=/usr/local/pgsql7.0/ --with-pgport=6666 --enable-debug

For some reason, current does not seem to allow "." in the
$PGDATA. I'm no sure why this happens at all. I guess it intends to
inhibit "./" or "../" for a security reason? If so, that would be
apparently an overkill.
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: "Ross J. Reedstrom"
Date:
Subject: sqgfault on initdb with current CVS
Next
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] TransactionStateData and AbsoluteTime