Re: initdb failing

From: Sachin Srivastava <sachin(dot)srivastava(at)enterprisedb(dot)com>
To: Scott Mead <scott(dot)lists(at)enterprisedb(dot)com>
Cc: rod(at)iol(dot)ie, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: initdb failing
Date: 2009-10-06 20:10:59
Message-ID: 4ACBA453.1080504@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/07/2009 01:24 AM, Scott Mead wrote:
>
> On Tue, Oct 6, 2009 at 3:09 PM, Sachin Srivastava
> <sachin(dot)srivastava(at)enterprisedb(dot)com
> <mailto:sachin(dot)srivastava(at)enterprisedb(dot)com>> wrote:
>
> On 10/06/2009 11:41 PM, Raymond O'Donnell wrote:
>
> On 06/10/2009 19:00, Sachin Srivastava wrote:
>
>
> fixing permissions on existing directory
> d:/base/netscope/pg/data ... ok
> * creating subdirectories ... initdb: could not create
> directory
> "d:/base/netscope/pg": File exists
> *initdb: data directory "d:/base/netscope/pg/data" not
> removed at user's
> request
>
> Could it be that the "..../data" directory isn't empty? I
> think initdb
> will fail if this is the case.
>
> its empty or i say its newly created.
>
>
> Because you're using the -n flag, after you run initdb once, the
> directory is left there. Delete the 'data' directory and try again.
Actually i put the -n and -d flags just to get more information about
what all has been created but they remain empty. Nevertheless tried
removing the old data directory and without -n option still got the same
output.
>
> --Scott
>

--
Regards,
Sachin Srivastava
www.enterprisedb.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Bartley 2009-10-06 20:23:22 Re: Fatal error on start
Previous Message Alvaro Herrera 2009-10-06 20:09:18 Re: attempted to lock invisible tuple - PG 8.4.1