Re: BUG #12785: server process (PID 2872) was terminated by exception 0xC0000005

Hi Francisco,

Thank you a lot for the answer, I really appreciate it. I will try to do what you have suggested and then I will let you know.

Just for information the problem has occurred again since the last email and always on the same query. I could understand a crash of the service on performing an update or a delete, but I have some difficulties to understand this on a select. If it was an hardware problem I would expect the service to crash also on other actions and not randomly (about once per week) only on a specific select (that is executed every 10 seconds).

Is there a way to write a select that is able to crash the service?

I will let you know the results of the hardware check after the planned restart.

Best regards
Daniele

From: Francisco Olarte [mailto:folarte(at)peoplecall(dot)com]<mailto:[mailto:folarte(at)peoplecall(dot)com]>
Sent: Friday, 20 February, 2015 5:51 PM
To: Daniele Posenato
Cc: pgsql-bugs(at)postgresql(dot)org<mailto:pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #12785: server process (PID 2872) was terminated by exception 0xC0000005

Hi Daniele:

On Thu, Feb 19, 2015 at 10:55 AM, <daniele(dot)posenato(at)smartec(dot)ch<mailto:daniele(dot)posenato(at)smartec(dot)ch>> wrote:
Operating system: W7 professionale 64 bit
​....
For an industrial application I have the same software running on 4
different PCs with the same characteristics and configurations. Each PC has
its how postgresql database. All 4 PC are doing the same things.
On one PC sometimes (about one per week) I get the server process (PID 2872)
was terminated by exception 0xC0000005.

​IIRC ​
0xC0000005
​ is the windows code for access violation, similar to SIGSEGV, which uses to be caused by stray pointers and similar things. Given you have this running in 4 machines and only got it in one it MAY be caused by faulty hardware ( ram flips a bit, corrupts a pointer, postgres uses pointer and gets the error ). If you can I would suggest doing a good RAM / disk / CPU test in that machine ( postgres is one of the candidates of getting hit by ram/disk faults because it uses a lot of them ).

​Best regards
Francisco Olarte.​

Roctest Barracuda scanned !