Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIGSEGV: segmentation violation on 0.38.0 #169

Closed
vvilaplana opened this issue Apr 1, 2021 · 2 comments · Fixed by #172
Closed

SIGSEGV: segmentation violation on 0.38.0 #169

vvilaplana opened this issue Apr 1, 2021 · 2 comments · Fixed by #172

Comments

@vvilaplana
Copy link

I just installed latest stable (0.38.0) on three VMs (Debian 10.8 with PostgreSQL 13.2) with different cpu/mem sizes and the three of them crashed with a signal SIGSEGV: segmentation violation error. The process restarts and it crashes again every 10 mins.

Please find attached traceback log:

pganalyze_segv.log

@lfittl
Copy link
Member

lfittl commented Apr 1, 2021

@vvilaplana Thanks for the report!

This looks like a crash in the normalization function. Could you send us a copy of the result of "SELECT * FROM pg_stat_statements" to support@pganalyze.com? (best as a CSV)

(I would recommend not posting here on GitHub, since Postgres does not always sanitize queries completely, which is why we run this second pass of normalization in the collcetor)

@lfittl
Copy link
Member

lfittl commented Apr 3, 2021

@vvilaplana The fix for this has been released now with the collector 0.38.1 - please let us know in case you're still seeing any issues!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants