Frank,
On Wed, Apr 30, 2003 at 07:05:53PM -0400, Frank Seesink wrote:
> Jason Tishler wrote:
> >The above is the crux of your problem. Until you get the above to
> >work, PostgreSQL is sure to fail. Sorry, but my only suggestion will
> >require some effort. I recommend building a (debug-able) version of
> >cygipc with tracing enabled. You may be able to determine what the
> >problem is from the trace output. Otherwise, there is always gdb...
>
> Oh, you're kidding, right? Please tell me you're kidding.
Sorry, no. However, see my next post...
> Man, what has happened since the last time I did a Cygwin PostgreSQL
> install?
Your previous post seemed to indicate that this was you first XP Pro
install (the others were on 2000). For some reasons, XP Pro seems to
give Cygwin PostgreSQL users problems...
> Is the answer to backpedal to an older version of PostgreSQL (and
> possibly CygIPC to boot)?
IMO, no.
> I guess what I'd like to know is, is anyone out there successfully
> running Windows XP Pro with the latest Cygwin and PostgreSQL 7.3.2?
I have been successful. AFAICT, XP Pro behaves identical to 2000 with
respect to Cygwin PostgreSQL.
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