> -----Original Message-----
> From: Jason Tishler [mailto:jason@tishler.net]
> Sent: 18 October 2001 17:47
> To: Dave Page
> Cc: Fu, Robert; 'Henshall, Stuart - WCP'; 'Steven Williams';
> pgsql-cygwin@postgresql.org
> Subject: Re: [CYGWIN] psql & cygncurses5.dll
>
>
> Dave,
>
> On Wed, Oct 17, 2001 at 09:05:36PM +0100, Dave Page wrote:
> > > -----Original Message-----
> > > From: Jason Tishler [mailto:jason@tishler.net]
> > > The above is terrible advice. The appropriate solution is to
> > > rerun setup.exe and reinstall the ncurses package that
> > > contains cygncurses5.dll. This has been mentioned numerous
> > > times on the Cygwin mailing list.
> >
> > I'm going to go and hide now as I can feel a telling-off on the way
> > from Jason :-) ...
>
> Sorry, Dave with a lead in like the above, I just couldn't
> resist... :,)
>
> > Whilst I agree that renaming is not a good idea,
>
> Let's put it this way, you were lucky that the above worked.
> The next time you may not be so lucky.
Luck didn't come into it - I didn't rename anything :-)
> > unfortunately the reality
> > is that searching that Cygwin list is not always the first
> thing that
> > springs to mind for some of us PostgreSQL users (pgsql-cygwin
> > maybe...).
>
> Since PostgreSQL under Windows relies on Cygwin, I strongly
> recommend searching the Cygwin list. Many "Cygwin PostgreSQL
> issues" are actually just "Cygwin issues."
I know, unfortunately human nature being what it is...
> Hopefully, my "telling-off" wasn't too harsh...
:-)
Regards, Dave.
