In message <[EMAIL PROTECTED]>you write:
>
>This is now in the doc directory as README.NT.
>
>
>[Charset iso-8859-1 unsupported, filtering to ASCII...]
>> These are the steps I used to compile and run PostgreSQL on Windows NT.
>> Notice that I have not verfied it after 24-3-99. In the coming week
In message <[EMAIL PROTECTED]>yo
u write:
>Hello,
>
>My company is pretty impressed with postgre on unix, but we also need a
>native port for nt (it is not an option to have our customers install cygwin
>on their production systems.) Ideally we would like to see the backend
>running as a native s
In message <[EMAIL PROTECTED]>you write:
>Hello folks,
>
>I'm running 6.5.1 on NT. I think I've applied all the patches to the
>ipc-daaemon, but after a while it starts hogging the CPU, even when no
>queries of any sort are being made (although there is a postmaster present).
>Reducing the priori
In message <[EMAIL PROTECTED]>you write:
>> Bruce,
>>
>> As I am not going to be able to help on the coding I won't try to
>> comment on it's dificulty.
>>
>> But I will ask what realistic expectations are for the current NT port
>> using cgywin. My current concern is that the installation is ve
In message <[EMAIL PROTECTED]>you write:
>
>Call this script postmasterangel.sh (as in guardian angel) and run it
>instead of the postmaster. Change the postmaster line in here to be
>your postmaster boot configuration options.
>
>
>This runs under linux. It will probably work under most un*x
>fla
In message <[EMAIL PROTECTED]>you write:
>
>Bruce Momjian writes:
> >
> > We run on NT now.
> >
>
>
>Has anyone tried running it as an NT service with the SRVANY.EXE
>program?
>
>
>--
>===
> Life is short. | Cr
In message <[EMAIL PROTECTED]>you write:
>>
>> Is this a standard (official) NT build that I can download from somewhere
>> or have you done your own conversion?
>
>It is part of the distribution. Get the tarball, and read the README.NT
>file on the web site or in the doc directory. We should
