Skip site navigation (1) Skip section navigation (2)

Re: Strange issue with initdb on 8.0 and Solaris automounts

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David Parker" <dparker(at)tazznetworks(dot)com>
Cc: "Kenneth Lareau" <elessar(at)numenor(dot)org>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Strange issue with initdb on 8.0 and Solaris automounts
Date: 2005-01-27 23:22:18
Message-ID: 21723.1106868138@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"David Parker" <dparker(at)tazznetworks(dot)com> writes:
> Did initdb previously just assume the -D path existed, and now it is
> trying to create the whole path, if necessary?

Pre-8.0 it was using mkdir(1), which might possibly contain some weird
workaround for this case on Solaris.

I suppose that manually creating the data directory before running
initdb would also avoid this issue, since the mkdir(2) loop is only
entered if we don't find the directory in existence.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Oliver JowettDate: 2005-01-27 23:27:05
Subject: Re: bug w/ cursors and savepoints
Previous:From: Oliver JowettDate: 2005-01-27 23:12:31
Subject: Re: bug w/ cursors and savepoints

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group