| From: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
|---|---|
| To: | Sachin Srivastava <sachin(dot)srivastava(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 19:54:30 |
| Message-ID: | d3ab2ec80910061254j34bcbdb8n5cef28dd0d88367b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Oct 6, 2009 at 3:09 PM, Sachin Srivastava <
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.
--Scott
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2009-10-06 19:57:38 | contrib/plantuner - enable PostgreSQL planner hints |
| Previous Message | pere roca | 2009-10-06 19:47:04 | interface for "non-SQL people" |