| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | garrett(at)rave(dot)io, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Re: BUG #17704: Monitoring Queries trigger 'Signal 7: Bus Error' After Creating Hash Partitioned Table |
| Date: | 2022-12-01 22:37:39 |
| Message-ID: | 1721828.1669934259@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On December 1, 2022 1:23:06 PM PST, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
>> Today I rolled out a new hash partitioned table with 1024 partitions to our
>> production DB (PostgreSQL 14.6 (Ubuntu 14.6-1.pgdg22.04+1) on
>> aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04)
>> 11.3.0, 64-bit). Previously we had been using pganalyze2 and pgmetrics with
>> no issue. Starting with the deployment of the new partitioned table anytime
>> pgmetrics or pganalyze2 would run we would get a SIGBUS and postgresql would
>> crash.
> Unfortunately that's not pointing anywhere obvious. We'll need a backtrace for the crash at least.
Indeed.
> I'm on my phone rn, so no link. But there's an article on the wiki with information about collecting a backtrace.
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-12-02 00:00:05 | Re: INFORMATION_SCHEMA.routines column routine_definition does not show the source |
| Previous Message | Andres Freund | 2022-12-01 21:59:03 | Re: BUG #17704: Monitoring Queries trigger 'Signal 7: Bus Error' After Creating Hash Partitioned Table |