Re: BUG #12785: server process (PID 2872) was terminated by exception 0xC0000005
От | Francisco Olarte |
---|---|
Тема | Re: BUG #12785: server process (PID 2872) was terminated by exception 0xC0000005 |
Дата | |
Msg-id | CA+bJJbxbn1hbeWddrbRDpSeSnJ09eVUMrWhV=LrfC7-6Dj1Azw@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #12785: server process (PID 2872) was terminated by exception 0xC0000005 (daniele.posenato@smartec.ch) |
Ответы |
Re: BUG #12785: server process (PID 2872) was terminated by
exception 0xC0000005
|
Список | pgsql-bugs |
Hi Daniele: On Thu, Feb 19, 2015 at 10:55 AM, <daniele.posenato@smartec.ch> wrote: > Operating system: W7 professionale 64 bit > =E2=80=8B.... > For an industrial application I have the same software running on 4 > different PCs with the same characteristics and configurations. Each PC h= as > 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. > =E2=80=8BIIRC =E2=80=8B 0xC0000005 =E2=80=8B is the windows code for access violation, similar to SIGSEGV, whi= ch 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 ). =E2=80=8BBest regards Francisco Olarte.=E2=80=8B
В списке pgsql-bugs по дате отправления: