ve been heavily used/tested with 6.5 and 7.0.
Has anyone seen this behavior? It looks like a blown pointer or counter
getting botched where WAL is attempting to write out of bounds.
Postgres WAL is new to me, so, did I miss something?
Thanks.
Matt Olson
The following bug has been logged online:
Bug reference: 2165
Logged by: Matt Olson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Windows XP Professional SP2
Description:excessive number of postgres.exe processes
Details:
This is
