Repository navigation
Clean up GPDB_14_MERGE_FIXME comments checked by testing - #2293
Open
chenjinbao1989 wants to merge 3 commits into
Open
chenjinbao1989 wants to merge 3 commits into
chenjinbao1989 wants to merge 3 commits into
Conversation
leborchuk
approved these changes
Nov 12, 2026
chenjinbao1989
force-pushed
the
fixme-cleanup-comments
branch
from
November 12, 2026 21:11
2deb4c7 to
84d1650
Compare
chenjinbao1989
enabled auto-merge (rebase)
November 12, 2026 21:11
chenjinbao1989
force-pushed
the
fixme-cleanup-comments
branch
from
November 13, 2026 01:17
84d1650 to
d5925cf
Compare
These FIXMEs have either been resolved already or match upstream: * nodeAgg.c: hash_mem_multiplier is already applied; drop the #if 0 hash_mem_limit. * functioncmds.c: procForm is already refetched from the new tuple; name the include_out_arguments argument of func_get_detail(). * execAmi.c: upstream lists T_TidRangeScan together with T_SeqScan too. * typecmds.c: upstream also uses typeNamespace for the multirange array. * distributedlog.c: the code already returns the more accurate value. * cdbmutate.c: ModifyTable no longer has a plans list; its subplan is lefttree, which the generic branch walks. * pg_dump.c: upstream does not check postDataSchemaOnly for DO_TABLE_ATTACH either. * copyfrom.c, copyto.c: a setvbuf() failure only affects performance. Also remove dead code: the #if 0 fetch_database_tuple() in vacuum.c, the unused REINDEX_REL_RECURSING_PARTITIONED_TABLE flag, leftover pg_pltemplate comments in gp_indexing.h, and the unused binary_upgrade_next_pg_type_oid variable (its declaration is already under #if 0 in binary_upgrade.h).
Comment-only change, no behavior change. Each FIXME was checked against the current code, then removed or turned into a plain "GPDB:" note. Resolved, so removed: * seclabel.c: these object types already return false. * tablecmds.c: foreign tables are already checked first. * createplan.c: ModifyTablePath has a single subpath. * CTranslatorDXLToPlStmt.cpp: splitUpdate is set, and the executor does not read partColsUpdated. * dependency.c: every object type tracked in pg_stat_last_* has a matching drop tracker. * decode.c, pg_control.h: 0xC0 is XLOG_NEXTRELFILENODE. * parse_partition_gp.c: DETACH CONCURRENTLY is disabled, so no partition can be pending detach and omit_detached makes no difference. * pg_dump.c: the multirange function signature matches, the additional function columns are queried unconditionally, and the commented-out asserts were inverted. * copyfrom.c: CopyInitDataParser() has two callers. * brin_bloom_optimizer.out, brin_multi_optimizer*.out: the plans do use a bitmap index scan, contrary to the comment. Intentional differences from upstream, so now documented as such: the horizon comments in procarray.c, analyze.c, nbtree.c, pathnodes.h, pg_proc.dat, varsup_test.c, pg_dump.c and type_sanity. gram.y: the keyword precedence list does not have to follow bare_label_keyword. Removing it causes shift/reduce conflicts, and a new conflicting keyword fails the build because of %expect 0. Postfix operators no longer exist, so describe the actual reason.
Comment-only change. * explain.c: intoClause isn't an optimizer problem. Without this assignment, EXPLAIN ANALYZE CREATE TABLE AS EXECUTE crashes the server, because ExplainOneQuery() doesn't run on that path. * procarray.c: the local xmin is safe for definitely_needed. An xid between the two bounds makes GlobalVis call ComputeXidHorizons(), which takes distributed snapshots into account. * utility.c: CREATE TABLE LIKE ... INCLUDING ALL with legacy subpartition syntax creates the indexes and constraints on all partitions, on the coordinator and the segments, so expanding statements at runtime works.
reshke
force-pushed
the
fixme-cleanup-comments
branch
from
November 14, 2026 14:54
d5925cf to
2676813
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Comment-only change.