Win32 Event log

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "PostgreSQL Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Win32 Event log
Date: 2004-08-12 08:03:17
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E41A76D7@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Under Win32 it is normal for serious errors to be recorded to the
systems event log as well as any log that the application may also be
writing (SQL Server is a good example of an app that does this).

The attached patch directs FATAL and PANIC elog's to the event log as
well as their normal destination. If the normal destination is the event
log, then they are not duplicated. This allows serious errors to be
picked up quickly and easily without swamping the event log (which
generally has limited size) with other events.

Please apply for beta 2...

Cheers, Dave.

Attachment Content-Type Size
elog.c.patch application/octet-stream 530 bytes

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Oliver Jowett 2004-08-12 11:25:03 Re: [HACKERS] SAVEPOINT syntax again
Previous Message Fabien COELHO 2004-08-12 07:34:16 Re: more massaging on pgxs postresql extension infrastructure