pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Rowley <drowley@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix Assert failure in WITH RECURSIVE UNION queries
Date: Thu, 19 Dec 2024 00:12:55 +0000
Message-ID: <E1tO49u-000Gle-Ns@gemulon.postgresql.org> (raw)

Fix Assert failure in WITH RECURSIVE UNION queries

If the non-recursive part of a recursive CTE ended up using
TTSOpsBufferHeapTuple as the table slot type, then a duplicate value
could cause an Assert failure in CheckOpSlotCompatibility() when
checking the hash table for the duplicate value.  The expected slot type
for the deform step was TTSOpsMinimalTuple so the Assert failed when the
TTSOpsBufferHeapTuple slot was used.

This is a long-standing bug which we likely didn't notice because it
seems much more likely that the non-recursive term would have required
projection and used a TTSOpsVirtual slot, which CheckOpSlotCompatibility
is ok with.

There doesn't seem to be any harm done here other than the Assert
failure.  Both TTSOpsMinimalTuple and TTSOpsBufferHeapTuple slot types
require tuple deformation, so the EEOP_*_FETCHSOME ExprState step would
have properly existed in the ExprState.

The solution is to pass NULL for the ExecBuildGroupingEqual's 'lops'
parameter.  This means the ExprState's EEOP_*_FETCHSOME step won't
expect a fixed slot type.  This makes CheckOpSlotCompatibility() happy as
no checking is performed when the ExprEvalStep is not expecting a fixed
slot type.

Reported-by: Richard Guo
Reviewed-by: Tom Lane
Discussion: https://postgr.es/m/CAMbWs4-8U9q2LAtf8+ghV11zeUReA3AmrYkxzBEv0vKnDxwkKA@mail.gmail.com
Backpatch-through: 13, all supported versions

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/093fc156b0ef69fdbe2a345c4ba6bca461c62631

Modified Files
--------------
src/backend/executor/execGrouping.c |  3 +--
src/test/regress/expected/with.out  | 15 +++++++++++++++
src/test/regress/sql/with.sql       | 12 ++++++++++++
3 files changed, 28 insertions(+), 2 deletions(-)



view thread (6+ messages)  latest in thread

Message-ID: <E1tO49u-000Gle-Ns@gemulon.postgresql.org>
Permalink:  ../E1tO49u-000Gle-Ns@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1tO49u-000Gle-Ns@gemulon.postgresql.org

 · 

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-committers@postgresql.org
  Cc: drowley@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Fix Assert failure in WITH RECURSIVE UNION queries
  In-Reply-To: <E1tO49u-000Gle-Ns@gemulon.postgresql.org>

* 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