Re: [PATCHES] Win32 Event log

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: "pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: [PATCHES] Win32 Event log
Date: 2004-08-12 22:14:03
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E41A7701@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32

> -----Original Message-----
> From: pgsql-hackers-win32-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org] On Behalf
> Of Bruce Momjian
> Sent: 12 August 2004 21:50
> To: Andrew Dunstan
> Cc: pgsql-hackers-win32
> Subject: Re: [pgsql-hackers-win32] [PATCHES] Win32 Event log
>
> I guess I am waiting for someone to report it doesn't work on
> NT4 SP4.
> How do we know it doesn't work?

OK, a little more research; NT4 with SP4 can read and write NTFS5
volumes. It *cannot* use many of the other NTFS5 features, including
reparse points which Andreas needed to implement symlinks.
(http://www.serverwatch.com/tutorials/article.php/10825_2239651_3 for
further analyis). Therefore, attempts to create tablespaces will
probably cause a crash.

In addition, the installer uses CreateProcessWithLogonW() to run initdb
at the service user. This API is not available on NT4, and although
there are others that *should* do the same job, Magnus failed could get
them to work despite us both trying to figure it out for some time. As
99.99% of Windows users will use the installer, I think this is perhaps
the most important reason to say that NT4 is in the 'at your own risk'
category.

Regards, Dave.

Responses

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Andrew Dunstan 2004-08-13 02:43:20 Re: Import from Linux to Windows
Previous Message Dave Page 2004-08-12 20:52:31 Re: [PATCHES] Win32 Event log