Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug] Wrong results: GROUP BY a constant expression returns one row for empty input

Abierto
  • ¿Algo no está bien?
#2,025 1 comentario 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, postgresql, sql
Área
databases

Línea de trabajo

Start by reproducing the two queries with optimizer = off and inspecting the provided EXPLAIN output, then trace how the PostgreSQL planner handles constant GROUP BY keys and multiphase aggregation. Done means empty input produces zero rows in both cases, without regressing non-empty inputs or the GPORCA path.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

type: Bug
Apache Cloudberry version

main branch

What happened

With the Postgres planner (optimizer = off), a query that groups by a constant expression returns one row when the input table is empty. A GROUP BY over zero input rows has zero groups, so the
correct answer is no rows.

GPORCA (optimizer = on) is not affected. Non-empty inputs are not affected — the extra row only appears when the input is empty.

What you think should happen instead

No response

How to reproduce
CREATE TABLE g(c0 boolean) DISTRIBUTED BY (c0);   -- left EMPTY
SET optimizer = off;

SELECT count(*) FROM g GROUP BY 'x'::text;
--  count
-- -------
--      0      <-- WRONG, expected 0 rows

SELECT 1 FROM g GROUP BY (0.25)::MONEY HAVING count(*) = 0;
--  ?column?
-- ----------
--         1   <-- WRONG, expected 0 rows

Expected in both cases: (0 rows).

The plan shows the grouping key disappearing and the final aggregate becoming a plain Aggregate, which always emits one row:

EXPLAIN (VERBOSE, COSTS OFF) SELECT count(*) FROM g GROUP BY 'x'::text;

 Finalize Aggregate
   Output: count(*), 'x'::text
   ->  Gather Motion 3:1  (slice1; segments: 3)
         Output: (PARTIAL count(*))
         ->  Partial GroupAggregate
               Output: PARTIAL count(*)
               ->  Seq Scan on public.g

Workarounds

  • SET optimizer = on; (GPORCA), or
  • SET gp_enable_multiphase_agg = off;
Operating System

any

Anything else

No response

Are you willing to submit PR?
  • Yes, I am willing to submit a PR!
Code of Conduct
Lenguaje dominante
C
Estrellas
1.4k
Forks
248
Merge medio
4 d 10 h
PR fusionados (30 d)
40

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/cloudberry

Todos los issues de apache/cloudberry

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.