Hi Tom, we've discovered more informations in the meanwhile.It seems that a bug in our backup tools caused a freeze in the database filesystem. The tool was stucked inside an xfs_freeze for a several minutes and caused the kernel to terminate processes locked waiting for write lock. One of this processes was postgresql.
I don't believe that was an issue on postgres-side. Bye, Rocco --- Rocco Zanni rocco.zanni@xxxxxxxxxxxx http://www.spreaker.com Il giorno 09/mag/12, alle ore 17:08, Tom Lane ha scritto:
Rocco Zanni <rocco.zanni@xxxxxxxxxxxx> writes:someone can help me understanding what happened in this crash logs? http://pastebin.com/0ruR4egmWhat was happening *before* the lines you showed? The information there seems to indicate that something got stuck whileholding the ProcStructLock, but there's no way to tell what or why fromthis much info. regards, tom lane
-- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Programming PHP] [Kernel Newbies] [PHP Classes] [Find Someone Nice] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]
![]() |
![]() |