Обсуждение: [BUGS] BUG #14462: Segment Fault recovery mode
The following bug has been logged on the website: Bug reference: 14462 Logged by: Lara Schembri Email address: lara.schembri@nyxgg.com PostgreSQL version: 9.3.15 Operating system: Centos 6.8 Description: Hi, While a running a vacuum, the database crashed for 20 seconds and went into recovery mode. < 2016-12-12 08:52:25.163 UTC >LOG: server process (PID 40436) was terminated by signal 11: Segmentation fault < 2016-12-12 08:52:25.163 UTC >DETAIL: Failed process was running: VACUUM (FREEZE, VERBOSE, ANALYZE); < 2016-12-12 08:52:25.163 UTC >LOG: terminating any other active server processes INFO: analyzing "public.<<table>>" INFO: "<<table>>": scanned 150000 of 14701352 pages, containing 6786398 live rows and 1026 dead rows; 150000 rows in sample, 665186112 estimated total rows vacuumdb: vacuuming of database "" failed: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. In /var/messages/log Dec 12 08:52:25 kernel: postmaster[40436]: segfault at 154f209d ip 000000000045da6c sp 00007ffe597fd7e0 error 4 in postgres[400000+519000] Can you please help on what might be the issue? Thanks and regards Lara -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
On Tue, Dec 13, 2016 at 10:30 PM, <lara.schembri@nyxgg.com> wrote: > While a running a vacuum, the database crashed for 20 seconds and went into > recovery mode. > > < 2016-12-12 08:52:25.163 UTC >LOG: server process (PID 40436) was > terminated by signal 11: Segmentation fault > < 2016-12-12 08:52:25.163 UTC >DETAIL: Failed process was running: VACUUM > (FREEZE, VERBOSE, ANALYZE); > < 2016-12-12 08:52:25.163 UTC >LOG: terminating any other active server > processes > > INFO: analyzing "public.<<table>>" > INFO: "<<table>>": scanned 150000 of 14701352 pages, containing 6786398 > live rows and 1026 dead rows; 150000 rows in sample, 665186112 estimated > total rows > vacuumdb: vacuuming of database "" failed: server closed the connection > unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > > In /var/messages/log > > Dec 12 08:52:25 kernel: postmaster[40436]: segfault at 154f209d ip > 000000000045da6c sp 00007ffe597fd7e0 error 4 in postgres[400000+519000] > > Can you please help on what might be the issue? You don't share much information here :( Do you have at least a core file or a backtrace? -- Michael -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs