From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Exit code -1073741819 |
Date: | 2013-08-04 11:35:34 |
Message-ID: | 51FE3C86.5030604@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2013-08-04 23:06:52 | Re: xlog min recovery request ... is past current point ... |
Previous Message | Jayadevan M | 2013-08-04 11:34:43 | Re: Migration from Symfoware to PostgreSQL-Constructor functions |