From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | kdavydenka(at)gmail(dot)ru |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17655: crash postgres by query |
Date: | 2022-10-20 14:57:55 |
Message-ID: | 3041792.1666277875@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Oct 20 14:52:21 server1 kernel: postgres[9328]: segfault at 1e88ff3 ip
> 00007f55ad8414ff sp 00007fff0031e7f8 error 4 in
> libc-2.17.so[7f55ad6eb000+1c3000]
> Oct 20 14:52:21 server1 abrt-hook-ccpp[9329]: Process 35274(postgres) of
> user 26 killed by SIGSEGV - dumping core
> log from postgres
> server process (PID 35274) was terminated by signal 11: Segmentation fault
> Failed process was running:
> select customer_id, birth_place from last_golden_record lgr where
> birth_place like U&'%\000A%'
With neither a stack trace nor a reproducible test case, there is
little anyone can do with this report.
There's some info about extracting stack traces from crashes at
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
but if you could make a self-contained test case that'd be
even better.
Also: it's possible that this is less about a software bug than
about corrupt data. Of course, we'd prefer the server not crash
on corrupt data, but sometimes that happens. A simple thing to do
that might help in such a case is to REINDEX whatever index(es)
the query is using. But first see
https://wiki.postgresql.org/wiki/Corruption
Also: the 10.x series will reach EOL next month. You should be
seriously working on updating to some later release branch.
Whether doing so will provide a fix for this problem is hard
to say, but it's not out of the question.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2022-10-20 15:06:11 | BUG #17658: Download release 15 without success |
Previous Message | PG Bug reporting form | 2022-10-20 14:57:38 | BUG #17657: Documentation links color |