Andrew Dunstan wrote:
>
> [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.
What is the downside of supporting NT4 if we can?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073