pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: m_lingbin@126.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
Date: Wed, 12 Feb 2025 08:38:34 +0100
Message-ID: <8ed9ba8971e114c3d6325c50a5f9fb6984140a01.camel@cybertec.at> (raw)
In-Reply-To: <18806-d70b0c9fdf63dcbf@postgresql.org>
References: <18806-d70b0c9fdf63dcbf@postgresql.org>

On Wed, 2025-02-12 at 07:01 +0000, PG Bug reporting form wrote:
> PostgreSQL version: 17.2
> Operating system:   CentOS Linux release 7.9.2009 (Core)
> Description:        
> 
> After upgrading PG17.2, testing found that when enable_rartitionwise_join is
> set to ON, when executing a query, if the main query and subquery have the
> same table, the query will report an error.
> 
> The database log shows the following error:
> LOG:  server process (PID 24796) was terminated by signal 6: Aborted
> DETAIL:  Failed process was running: select * from test t join orders o on
> t.order_id =o.order_id where t.order_id in (select order_id from orders);
> LOG:  terminating any other active server processes

That is a crash that may well indicate a PostgreSQL bug.

However, without a way to reproduce the behavior, we won't be able to fix
the problem.  Try to come up with a self-contained test case.  It would
also be interesting to know which PostgreSQL extensions are present.

Yours,
Laurenz Albe

-- 

*E-Mail Disclaimer*
Der Inhalt dieser E-Mail ist ausschliesslich fuer den 
bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat 
dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, 
dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder 
Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich 
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.

*CONFIDENTIALITY NOTICE & DISCLAIMER
*This message and any attachment are 
confidential and may be privileged or otherwise protected from disclosure 
and solely for the use of the person(s) or entity to whom it is intended. 
If you have received this message in error and are not the intended 
recipient, please notify the sender immediately and delete this message and 
any attachment from your system. If you are not the intended recipient, be 
advised that any use of this message is prohibited and may be unlawful, and 
you must not copy this message or attachment or disclose the contents to 
any other person.





view thread (22+ messages)  latest in thread

Message-ID: <8ed9ba8971e114c3d6325c50a5f9fb6984140a01.camel@cybertec.at>
Permalink:  ../8ed9ba8971e114c3d6325c50a5f9fb6984140a01.camel@cybertec.at/
Also on:    postgresql.org/message-id/8ed9ba8971e114c3d6325c50a5f9fb6984140a01.camel@cybertec.at

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: laurenz.albe@cybertec.at, m_lingbin@126.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  In-Reply-To: <8ed9ba8971e114c3d6325c50a5f9fb6984140a01.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox