From: | Jason Tishler <jason(at)tishler(dot)net> |
---|---|
To: | Frank Seesink <frank(at)mail(dot)wvnet(dot)edu> |
Cc: | Pgsql-Cygwin <pgsql-cygwin(at)postgresql(dot)org> |
Subject: | Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / |
Date: | 2003-05-05 11:30:59 |
Message-ID: | 20030505113059.GB556@tishler.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cygwin |
Frank,
On Fri, May 02, 2003 at 06:42:14PM -0400, Frank Seesink wrote:
> Set system environment variable CYGWIN=nontsec, rebooted, and tried it
> all again. BZZZZ! Wrong! Thanks for playing. Nope, still no good.
>
> So ntsec isn't the issue.
>
> Next question: I notice on the webpage for CygIPC, Jason, that you
> are a large contributor to fixes that are in 1.13. The webpage makes
> it sound, however, like CygIPC 1.11 and 1.13 are basically the same
> ("1.13 is a backward compatible, drop-in replacement for
> cygipc-1.11").
Yes, 1.11 and 1.13 are basically the same. However, the cygipc
maintainer changed at least one pathname (i.e., /tmp/cygipc vs.
/tmp/cygipc_) which breaks compatibility.
> Would it make sense to try CygIPC 1.11 to see if that worked?
No.
> Or is it a known fact that PostgreSQL 7.3.2 must have CygIPC 1.13?
> From all I gathered, 1.13 was required for 7.3.2, so I never tried
> going backwards. Just figured I'd ask to be sure.
Yes, see above. Actually, IIRC, 1.13-2 is required -- even 1.13-1 won't
work. Sigh...
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Tishler | 2003-05-05 11:56:33 | Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / |
Previous Message | Jason Tishler | 2003-05-05 11:25:37 | Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / |