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: elog.c.patch
Description: elog.c.patch

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to