From: | Sean Massey <sean(dot)f(dot)massey(at)gmail(dot)com> |
---|---|
To: | Cameron Vogt <cvogt(at)automaticcontrols(dot)net> |
Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL 17 Segmentation Fault |
Date: | 2024-10-02 20:08:14 |
Message-ID: | CAJfn5C0Kqn52wxVqRBaFSyTf4O6Avo6xoLoS76SWysRQWjx4Rw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Can you reproduce this with a small subset of schema and data on another
installation of 17? Could you share the DDL to reproduce this failure case?
Can you capture the core dump?
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
On Thu, 3 Oct 2024 at 04:16, Cameron Vogt <cvogt(at)automaticcontrols(dot)net>
wrote:
> I recently upgraded a database from PostgreSQL 11.22 to 17.0. One of my
> queries which ran fine in PostgreSQL 11 is now causing a segmentation fault
> in 17. The log file contains this message: *"server process (PID 7635)
> was terminated by signal 11: Segmentation fault","Failed process was
> running: SELECT DISTINCT ON (""tasks"".""gid"")*. I tried to delete
> pieces of the query and rerun it to see if I could determine which part is
> causing the fault. I attached the minimal query I came up with. If I try to
> delete any random piece out of the minimal query, it suddenly works again
> (even just a single line like line #2). I have no idea what is going on
> with it, but I think it is a bug.
>
>
> Cameron Vogt | Software Developer
>
> Direct:314-756-2302 | Cell: 636-388-2050
> cvogt(at)automaticcontrols(dot)net
>
> 1585 Fencorp Drive
> <https://www.google.com/maps/dir/38.5384448,-90.43968/Automatic+Controls+Equipment+Systems,+Inc.+Fenton,+MO+63026/@38.5371308,-90.448053,16z/data=!3m1!4b1!4m9!4m8!1m1!4e1!1m5!1m1!1s0x87d8cfa7d0262fa3:0x8de9b691c07a1768!2m2!1d-90.4476712!2d38.5358207>
>
> <https://www.google.com/maps/dir/38.5384448,-90.43968/Automatic+Controls+Equipment+Systems,+Inc.+Fenton,+MO+63026/@38.5371308,-90.448053,16z/data=!3m1!4b1!4m9!4m8!1m1!4e1!1m5!1m1!1s0x87d8cfa7d0262fa3:0x8de9b691c07a1768!2m2!1d-90.4476712!2d38.5358207>Fenton,
> Missouri 63026
> <https://www.google.com/maps/dir/38.5384448,-90.43968/Automatic+Controls+Equipment+Systems,+Inc.+Fenton,+MO+63026/@38.5371308,-90.448053,16z/data=!3m1!4b1!4m9!4m8!1m1!4e1!1m5!1m1!1s0x87d8cfa7d0262fa3:0x8de9b691c07a1768!2m2!1d-90.4476712!2d38.5358207>
> [image: ACES.png]
> [image: SupportLink.png] <https://automaticcontrols.net/request-support/>
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2024-10-02 20:57:48 | Re: BUG #18643: EXPLAIN estimated rows mismatch |
Previous Message | Cameron Vogt | 2024-10-02 17:16:45 | PostgreSQL 17 Segmentation Fault |