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

Re: INITDB error

From: "Mike Leahy" <mgleahy(at)fes(dot)uwaterloo(dot)ca>
To: "'Mike Leahy'" <mgleahy(at)fes(dot)uwaterloo(dot)ca>,<pgsql-cygwin(at)postgresql(dot)org>
Cc: <jpraz(at)dplanet(dot)ch>
Subject: Re: INITDB error
Date: 2003-12-15 18:00:23
Message-ID: 000601c3c335$50784c50$2eb54bd8@MGLEAHY (view raw, whole thread or download thread mbox)
Lists: pgsql-cygwin

I think I figured out at least what I was doing wrong.  I wiped my Cygwin
folder and started from scratch (again), then reinstalled with the
setup.exe.  The only thing I did different this time was select the "UNIX"
text style option in the installer, and the initdb script works.  I've
always been using DOS style before, and it never caused a problem.

In my case, it wasn't a big deal to reinstall everything, but perhaps I
could have just changed one of the environment variables - I'm guessing
MAKE_MODE might be it, but I really have no clue and I don't see anything in
the installed docs about switching from dos to unix.


-----Original Message-----
From: pgsql-cygwin-owner(at)postgresql(dot)org
[mailto:pgsql-cygwin-owner(at)postgresql(dot)org] On Behalf Of Mike Leahy
Sent: December 13, 2003 3:24 PM
To: pgsql-cygwin(at)postgresql(dot)org
Cc: jpraz(at)dplanet(dot)ch
Subject: Re: [CYGWIN] INITDB error


I'm back to the same problem as well.  Just to be sure I reinstalled 
everything to do with Cygwin (again), and now I get the same error.  I can't

even guess why it worked the first try, since I haven't done anything 
different this second time.  Is there something we should be looking out


(sorry if I sent this twice)

-----Original Message-----
From: pgsql-cygwin-owner(at)postgresql(dot)org [mailto:pgsql-cygwin-
owner(at)postgresql(dot)org] On Behalf Of Jean-Pierre Praz
Sent: December 10, 2003 7:53 PM
To: pgsql-cygwin(at)postgresql(dot)org
Subject: Re: [CYGWIN] INITDB error


in my installation on cygwin/winXP there is exactly the same error. i 
updated cygwin before installing postgres 7.4.1, so i don't know what more 
i could update there. before i ran postgres 7.3.x without any troubles.

does anyone have an idea how to solve this?
any help or ideas are welcome.


Running in noclean mode.  Mistakes will not be cleaned up.
The files belonging to this database system will be owned by user "...".
This user must also own the server process.

The database cluster will be initialized with locale C.

creating directory 
/usr/src/postgresql-7.4-1/src/test/regress/./tmp_check/data... ok
creating directory 
/usr/src/postgresql-7.4-1/src/test/regress/./tmp_check/data/base... ok
creating directory 
/usr/src/postgresql-7.4-1/src/test/regress/./tmp_check/data/global... ok
creating directory 
/usr/src/postgresql-7.4-1/src/test/regress/./tmp_check/data/pg_xlog... ok
creating directory 
/usr/src/postgresql-7.4-1/src/test/regress/./tmp_check/data/pg_clog... ok
selecting default max_connections... 100
selecting default shared_buffers... 1000
creating configuration files... ok
creating template1 database in 
/usr/src/postgresql-7.4-1/src/test/regress/./tmp_check/data/base/1... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ERROR:  end-of-copy marker does not match 
previous newline style
CONTEXT:  COPY tmp_pg_description, line 1542: ""

initdb: failed
initdb: data directory 
"/usr/src/postgresql-7.4-1/src/test/regress/./tmp_check/data" not removed 
at user's request

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?


This mail sent through

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

In response to


pgsql-cygwin by date

Next:From: Mike LeahyDate: 2003-12-15 19:54:45
Subject: createdb - pq.dll
Previous:From: Leeuw van der, TimDate: 2003-12-15 14:28:56
Subject: Re: problem upgrading to PostgreSQL 7.4

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