[Bug] Correct classification of plan nodes

Abierto
#2,268 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
58/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, postgresql

Línea de trabajo

Read is_plan_node in src/backend/cdb/cdbllize.c and inspect the node definitions in plannodes.h that determine the T_Plan_Start..T_Plan_End range. Check whether the range and the listed exceptions classify plan nodes correctly, then add or update focused tests for serialization classification. Done means non-plan nodes are excluded and actual plan nodes are recognized.

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

Descripción

type: Bug
Apache Cloudberry version

main

What happened

Some nodes that are not plan nodes have been incorrectly categorized as plan nodes, while some actual plan nodes have failed to be classified as such. We need to categorize these nodes correctly; otherwise, it could lead to issues regarding the correctness of serialization. What follows may not be exhaustive.

diff --git a/src/backend/cdb/cdbllize.c b/src/backend/cdb/cdbllize.c
index 31749f0305b..b4bdf5bf863 100644
--- a/src/backend/cdb/cdbllize.c
+++ b/src/backend/cdb/cdbllize.c
@@ -1430,6 +1430,24 @@ is_plan_node(Node *node)
 	if (node == NULL)
 		return false;
 
+	/*
+	 * Node tags are generated in the order the structs appear in
+	 * plannodes.h, so the T_Plan_Start..T_Plan_End range is not exact:
+	 * NestLoopParam and ExternalScanInfo are defined among the plan nodes
+	 * but are not Plans, and PartitionSelector is defined after
+	 * PlanRowMark but is one.
+	 */
+	switch (nodeTag(node))
+	{
+		case T_NestLoopParam:
+		case T_ExternalScanInfo:
+			return false;
+		case T_PartitionSelector:
+			return true;
+		default:
+			break;
+	}
+
 	if (nodeTag(node) >= T_Plan_Start && nodeTag(node) < T_Plan_End)
 		return true;
 	return false;
What you think should happen instead

No response

How to reproduce

Cannot be exhaustively listed

Operating System

NAME="Rocky Linux" VERSION="9.5 (Blue Onyx)"

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
273
Merge medio
4 d 6 h
PR fusionados (30 d)
105

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.