Yes, I agree with you that it must be upgraded to a supported version but as the developer has not homologated the system to some new PG versions yet I need to find out some way to fix it with 8.2.
Will try to install PG in another windows box, copying the data directories over the network and see if I can at least take a pg_dump from the database as it is currently not possible.
Another possibility is to copy the data directory from the windows box to a linux with PG 8.2 and start the database there, does this approach has any possibility of success?
On 08/04/2013 02:41 AM, Carlos Henrique Reimer wrote: > Hi, > > I have a Windows box running Windows Server 2003 Enterprise Edition > Service Pack 2 with PostgreSQL 8.2.23 and getting a server crash while > trying to select a table: > > select * from "TOTALL.tt_est" where assina=' kdkd' ; > > Dumping the table with pg_dump or creating indexes in this table produce > the same error. > > 2013-07-30 21:35:47 LOG: server process (PID 2004) exited with exit > code -1073741819
This looks like an invalid memory access error. This could be caused by practically anything - hardware issues, malware hook DLLs, drivers, antivirus, you name it.
You're using PostgreSQL 8.2, so honestly your first step is probably "just upgrade". 8.2 is old and unsupported (www.postgresql.org/support/versioning/), so there's very little point investigating a bug until it can be reproduced in a current version.
Can you `pg_dump` your database? If so, follow the upgrade instructions in the documentation to get onto a current, supported version. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
