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 20:11:00 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E41A76FD@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 18:51
> To: Andrew Dunstan
> Cc: pgsql-hackers-win32
> Subject: Re: [pgsql-hackers-win32] [PATCHES] Win32 Event log
>
> What is the downside of supporting NT4 if we can?
- Possible loss of tablespace support.
- No way to start PostgreSQL from an admin account without buying the
resource kit to get runas.
- The installer will not be able to initdb (or subsequently install the
service without risking it failing to start if the users down't login to
the service account and initdb manually before restarting).
- The installer will require the user to manually install the Windows
Installer service first if they don't aready have it (not difficult,
just annoying).
- I suspect few of us have NT4 around to help debug platform specific
problems.
- No custom event logs (if we go that route).
There's probably more that I haven't though of.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-08-12 20:11:49 | Re: [PATCHES] Win32 Event log |
Previous Message | Dave Page | 2004-08-12 20:04:23 | Re: [PATCHES] Win32 Event log |