Thread: Troubles with the 7.4.2-1 cygwin package

7.4.2 now uses cygserver to run postgres as a service.  Make sure you
have installed cygserver, included it in your path, delete the current
postgres service you have installed, and finally reinstall the postgres
service using cygserver instead of the ipc-daemon2.

mike
On Mon, 2004-06-14 at 13:14, Tim J Hart wrote:
> I tried installing the 7.4.2 package today with no success.
>
> I understand that because of a bug fix between 7.4.1 and 7.4.2, a
> dump/restore cycle is recommended. So I dumped my current db's,
> installed 7.4.2 via cygwin's setup application, logged in as my
> postgres user, and proceeded to init.
>
> Instead of seeing the normal progress of initdb, I saw the
> following...
>
> $initdb -D /usr/local/data
> ...
> selecting default max_connections... Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> 10
> selecting default shared_buffers... Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> 50
> ... #normal messages here...
>
> creating template1 database in /usr/local/data/base/1... Signal 12
>
> initdb failed
> $
>
> I'm running Windows XP service pack 1
> uname -a returns
> CYGWIN_NT-5.1 SQUEEZEBOX 1.5.10(0.116/4/2) 2004-05-25 22:07 i686
> unknown unknown Cygwin
>
> I Reinstalled 7.4.1-3, and executed the normal initdb/restore cycle
> without a problem at all.