Re: [PATCHES] Win32 Event log

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-hackers-win32 <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: [PATCHES] Win32 Event log
Date: 2004-08-12 17:15:02
Message-ID: 411BA596.3060105@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32 pgsql-patches


[redirecting]

Dave Page wrote:

>
>>In the third place, no one is going to have any difficulty
>>picking out PANICs from "other events" ;-)
>>
>>
>
>Finding them is not so much the problem - it's the fact that the event
>log on Windows has a limited size (default 1024Kb on XP) and will
>overwrite old events as required. The sort of output you might see from
>a busy PostgreSQL server could potentially wipe out relatively new
>entries made by other apps.
>
>One possible solution would be to use our own event log which is
>possible in 2K+, (but not NT).
>
>
>
>
>

I am more and more coming to the conclusion that we should either remove
NT4 as a supported platform, or at least surround it with very
significant caveats. M$ is about to end the last remaining bit of
support for it, and has already stopped publishing non-security fixes.

It looks like there are lots of legacy installations still out there
(heck, I see lots of RH7.3 and it's also out of support).

But there isn't any legacy native W32 Postgres, so we would not be
affecting any legacy users by not supporting NT4.

Thoughts?

cheers

andrew

In response to

Responses

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Bruce Momjian 2004-08-12 17:50:33 Re: [PATCHES] Win32 Event log
Previous Message Mark Cave-Ayland 2004-08-12 16:47:52 Re: GUC variables invisible to contrib/ modules

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-08-12 17:49:59 Re: [HACKERS] SAVEPOINT syntax again
Previous Message Bruce Momjian 2004-08-12 16:47:14 Re: [BUGS] 8.0.0beta1: -lpthread missing