| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Yuri Zamyatin <yuri(at)yrz(dot)am>, Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade |
| Date: | 2025-10-15 22:51:35 |
| Message-ID: | CAApHDvoEJ6z89TQxtC_Zi6xtGyTNzcrtJs=6MMO_-vybWQE6gA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, 16 Oct 2025 at 11:45, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> On Thu, 16 Oct 2025 at 03:21, Yuri Zamyatin <yuri(at)yrz(dot)am> wrote:
> > In 1-2 minutes, 5 processes died with segfault.
>
> Perfect. Thank you.
>
> It seems to be some more forgotten EPQ stuff from d47cbf474. Amit got
> some of these in 8741e48e5, but evidently the test case didn't do
> pruning during execution, (only init plan pruning) so the partition
> directory wasn't needed.
I forgot to mention, this isn't the same thing as the
tts_minimal_store_tuple() issue you first reported, so if there is a
problem there, this one has nothing to do with it.
Any chance of a self-contained test case for the enable_hashagg=on crash?
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-10-15 23:07:24 | Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables. |
| Previous Message | David Rowley | 2025-10-15 22:45:12 | Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade |