-
Notifications
You must be signed in to change notification settings - Fork 34
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
Segmentation fault #79
Comments
Right after server recovery, I was able to properly squeeze that table using the same command.
|
Do you happen to have a core dump? Backtrace of that segfault might be useful. |
Doesn't look like postgres was configured to core dump, unfortunately. I will configure postgres to do it and try to reproduce. |
Some extra logs that may be useful:
|
It could perhaps help if we knew at which address the Can you please try to arrange the server for core dumps? (https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD) If not, I need a test case that crashes the server after a "reasonable" number of tries. I tried what you described above several times, but with no luck. |
So, I did the required configuration, but I was unable to reproduce the crash, that's going to be a hard one. |
Thanks. I'm trying to enhance my test application to increase the chance that I can reproduce the problem myself. |
public.table
database=# SELECT squeeze.squeeze_table('public', 'table');
Postgresql is version 17 and pg_squeeze is installed though
apt install postgresql-17-squeeze
from official postgres repos.Postgres logs:
The text was updated successfully, but these errors were encountered: