Re: Use generation memory context for tuplestore.c

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Use generation memory context for tuplestore.c
Date: 2024-07-05 04:57:26
Message-ID: CAApHDvqT=6KWWb_dii+W0risak6bYBe2yu7e4oUtZoiNOeORKg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 5 Jul 2024 at 16:00, Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> Please look at a segfault crash introduced with 1eff8279d:
> CREATE TABLE t1(i int);
> CREATE TABLE t2(i int) PARTITION BY RANGE (i);
> CREATE TABLE t2p PARTITION OF t2 FOR VALUES FROM (1) TO (2);
>
> EXPLAIN ANALYZE SELECT * FROM t1 JOIN t2 ON t1.i > t2.i;
>
> Leads to:
> Core was generated by `postgres: law regression [local] EXPLAIN '.
> Program terminated with signal SIGSEGV, Segmentation fault.
>
> #0 0x000055c36dbac2f7 in tuplestore_storage_type_name (state=0x0) at tuplestore.c:1476
> 1476 if (state->status == TSS_INMEM)

Thanks for the report. I've just pushed a fix in 53abb1e0e.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-07-05 05:19:54 Re: pg_ctl start may return 0 even if the postmaster has been already started on Windows
Previous Message Michael Paquier 2024-07-05 04:52:31 Re: Flush pgstats file during checkpoints