{"kind": "plan", "major": "18", "item": {"slug": "bitmapor", "name": "BitmapOr", "name_zh": "BitmapOr", "category": "Bitmap", "summary": "Unions bitmaps produced by its child plans.", "aliases": ["BitmapOr", "T_BitmapOr"], "content_hash": "7f9182fb8e68ec6e2d9cef66a3b2e1134d354dc29d296ee25b10a06ecfec7c3f", "versions": {"10": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "7ce2244a52bf2d4172e1b03c50e1ab2505225fe2806a50e3f068405637157a27", "archive_sha256": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9"}, {"url": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "66152ac93c470e2705adfef9a4c10ad3aa1beccb7baccf0b16dd96f3d59a0ec0", "archive_sha256": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=10", "label": "EXPLAIN"}, {"url": "/docs/10/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/10/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=10", "label": "work_mem"}], "release": {"ref": "PostgreSQL 10.23 source archive", "label": "10.23", "major": "10", "channel": "historical", "revision": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9", "source_url": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "line": 918, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:918", "sha256": "a785298532047cfeda969e78c3597a343dc1c56d61ba85830b0f16a02a14b5a1", "archive_sha256": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9"}, {"url": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "line": 199, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:199", "sha256": "cea76648bb38ae55f18f989768bee1a4ee025691ceea0f86bccb29dcdc166acc", "archive_sha256": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9"}, {"url": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "7ce2244a52bf2d4172e1b03c50e1ab2505225fe2806a50e3f068405637157a27", "archive_sha256": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9"}, {"url": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "d562c321108844798cd234303fffb618f13d4ee3f3a5ac79bfd963b077e47c22", "archive_sha256": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9"}, {"url": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "66152ac93c470e2705adfef9a4c10ad3aa1beccb7baccf0b16dd96f3d59a0ec0", "archive_sha256": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9"}, {"url": "/docs/10/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 10.23 \u00b7 using-explain", "sha256": "a4b4304aedb0a2da0145cc7c35b03b319a5c7ee3df35a8ef84ab6d3a610f98f3"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "11": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "fe542bc106cc764b0fca94e021870478945c29fafb5d08e8f2e99eeb3762a632", "archive_sha256": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0"}, {"url": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "a47e915ced1ae75d21b8d7b7b67ae09c4bf230069208aa5d9f5b6c2ca6ae85d1", "archive_sha256": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=11", "label": "EXPLAIN"}, {"url": "/docs/11/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/11/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=11", "label": "work_mem"}], "release": {"ref": "PostgreSQL 11.22 source archive", "label": "11.22", "major": "11", "channel": "historical", "revision": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0", "source_url": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "line": 1043, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1043", "sha256": "9df8400c1a4377179572ceb916d6020fca4e2760f74bf416d77ed97476523bbd", "archive_sha256": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0"}, {"url": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "line": 199, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:199", "sha256": "95ef4d4a5df4c29f14af9763fae2c530449bdacdf3853d9ff297adf1fed6153b", "archive_sha256": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0"}, {"url": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "fe542bc106cc764b0fca94e021870478945c29fafb5d08e8f2e99eeb3762a632", "archive_sha256": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0"}, {"url": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "5e0511194183800e8d6eb293fd4b40639c7d3118e2d199c8e7865ba4fa4cf67f", "archive_sha256": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0"}, {"url": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "a47e915ced1ae75d21b8d7b7b67ae09c4bf230069208aa5d9f5b6c2ca6ae85d1", "archive_sha256": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0"}, {"url": "/docs/11/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 11.22 \u00b7 using-explain", "sha256": "8411bc78085d4737e32d7cca103d859da6c6539e33ec5e2fba46e74c6f199d8a"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "12": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "00f6348b2dd4ed868e6f2f8dae8662651547db206664e4682c3557c6a798f19b", "archive_sha256": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b"}, {"url": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "8a18d2e770adab40a9172ebc6895501ec22f650b479c4e9ce44ca010c57ad24d", "archive_sha256": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=12", "label": "EXPLAIN"}, {"url": "/docs/12/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/12/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=12", "label": "work_mem"}], "release": {"ref": "PostgreSQL 12.22 source archive", "label": "12.22", "major": "12", "channel": "historical", "revision": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b", "source_url": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "line": 1114, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1114", "sha256": "d02ea84fdaa201de5d9360645a9f24bfbd2c31f7d45a639e09560ac0e6b6471d", "archive_sha256": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b"}, {"url": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "line": 199, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:199", "sha256": "311b17379fe54e3f342fe5ad41c43afbdfa1b844978db2bb2eb22b82520d3256", "archive_sha256": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b"}, {"url": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "00f6348b2dd4ed868e6f2f8dae8662651547db206664e4682c3557c6a798f19b", "archive_sha256": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b"}, {"url": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "b0c4a0aeb48660ce06e5e700d5529ca9066fd16682bd15783d6e71b5420b07b0", "archive_sha256": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b"}, {"url": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "8a18d2e770adab40a9172ebc6895501ec22f650b479c4e9ce44ca010c57ad24d", "archive_sha256": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b"}, {"url": "/docs/12/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 12.22 \u00b7 using-explain", "sha256": "06297525f2180b07e752837a3351be9c871b56559f535bcd0a67dec9baac10c0"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "13": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "96e6d1ff7286faf41be8aaac14215f63475484da8c54f8aca1ca91500e0c01d1", "archive_sha256": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6"}, {"url": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "a0823f106dd0af7415c44a788a8b258dc13afc6dab320d0dec0a2d17f418fdb8", "archive_sha256": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=13", "label": "EXPLAIN"}, {"url": "/docs/13/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/13/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=13", "label": "work_mem"}], "release": {"ref": "PostgreSQL 13.23 source archive", "label": "13.23", "major": "13", "channel": "historical", "revision": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6", "source_url": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "line": 1172, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1172", "sha256": "541713e0e7f1c9cc352c2b6028964d440c19d2678a4463000094c24a88c1e730", "archive_sha256": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6"}, {"url": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "line": 199, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:199", "sha256": "d085ee99acfa00587e6ade3a1d9f8108a0566beedbbee3f54a50c9fc0cc2e875", "archive_sha256": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6"}, {"url": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "96e6d1ff7286faf41be8aaac14215f63475484da8c54f8aca1ca91500e0c01d1", "archive_sha256": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6"}, {"url": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "dcb296833777b02008c4b6bae8e8f7c6423b7ffba21f36702597c9d596d039ab", "archive_sha256": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6"}, {"url": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "a0823f106dd0af7415c44a788a8b258dc13afc6dab320d0dec0a2d17f418fdb8", "archive_sha256": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6"}, {"url": "/docs/13/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 13.23 \u00b7 using-explain", "sha256": "650fd8629382d5dc8f9f8412c50ec5f32442a9ad2f98ca88e5348a7c2bd0ac7a"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "14": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "b0d2caaac97ee1d68adb67d184a4e9340148a782b72a75891fcfb598aa85e783", "archive_sha256": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897"}, {"url": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "6b86639c01e2be18b9e08a99d5aa46e09747cade936cc703d9d30bfe8d61fa1c", "archive_sha256": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=14", "label": "EXPLAIN"}, {"url": "/docs/14/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/14/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=14", "label": "work_mem"}], "release": {"ref": "PostgreSQL 14.24 source archive", "label": "14.24", "major": "14", "channel": "stable", "revision": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897", "source_url": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "line": 1208, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1208", "sha256": "e091be4e2a083b8dea39ccd09beedede22c1716ef974da66c214a44f48be8c41", "archive_sha256": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897"}, {"url": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "line": 201, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:201", "sha256": "72da1c5ad457f1d92a39ab73531701794df858419e3b89d6e6cb7079634e68fa", "archive_sha256": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897"}, {"url": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "b0d2caaac97ee1d68adb67d184a4e9340148a782b72a75891fcfb598aa85e783", "archive_sha256": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897"}, {"url": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "302f51a16b570dba7ec4e7bc045f7df5800d21630280354d1a24025f3baec75d", "archive_sha256": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897"}, {"url": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "6b86639c01e2be18b9e08a99d5aa46e09747cade936cc703d9d30bfe8d61fa1c", "archive_sha256": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897"}, {"url": "/docs/14/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 14.24 \u00b7 using-explain", "sha256": "7f5ab59cb21a035ada45ea3426c5d1cca3f781273483677f73fdd76753555206"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel", "Async"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "15": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "d6831e8f332aba276ea49ee76e308e60ad324800640ac5722556af7b337cb030", "archive_sha256": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89"}, {"url": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "4abf4a8e67412488d65490b4e292043351122be09f03af97150b384dc7ee11bb", "archive_sha256": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=15", "label": "EXPLAIN"}, {"url": "/docs/15/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/15/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=15", "label": "work_mem"}], "release": {"ref": "PostgreSQL 15.19 source archive", "label": "15.19", "major": "15", "channel": "stable", "revision": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89", "source_url": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "line": 1211, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1211", "sha256": "bb3b442d0f1b098aa8707335250102f027a596cd94117308bd16d1d36b258f5c", "archive_sha256": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89"}, {"url": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "line": 201, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:201", "sha256": "19836c50a272741a4eac653541e655437c2e00710a541e5348d6a277d0669d7c", "archive_sha256": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89"}, {"url": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "d6831e8f332aba276ea49ee76e308e60ad324800640ac5722556af7b337cb030", "archive_sha256": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89"}, {"url": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "fb4a4c8165495299131173680bc02a950d88e1ff610231fd97997bc0c9afc1d7", "archive_sha256": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89"}, {"url": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "4abf4a8e67412488d65490b4e292043351122be09f03af97150b384dc7ee11bb", "archive_sha256": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89"}, {"url": "/docs/15/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 15.19 \u00b7 using-explain", "sha256": "d1f509457c647da453d2575c772d91022a0f115dd84f9a3b20f5ff25a243648f"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel", "Async"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "16": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "d29259efccb1b04f34599a20ae7ccb9970fc6fe2e19f39090b821b55399fbc41", "archive_sha256": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"}, {"url": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "d0a2549a532f65299aea5599ee1bedffe47101a07d0de21bec07068547ae237e", "archive_sha256": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=16", "label": "EXPLAIN"}, {"url": "/docs/16/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/16/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=16", "label": "work_mem"}], "release": {"ref": "PostgreSQL 16.15 source archive", "label": "16.15", "major": "16", "channel": "stable", "revision": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed", "source_url": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "line": 1244, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1244", "sha256": "8e017f0116dbea471339b40c37a667cc9f95039e7e0329c783e5e8ce194de7e1", "archive_sha256": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"}, {"url": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "line": 201, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:201", "sha256": "e48c08e555f8cb4e4bb43df516c4b8906ce9bc374b2a745d98a1fc8c22cc5099", "archive_sha256": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"}, {"url": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "d29259efccb1b04f34599a20ae7ccb9970fc6fe2e19f39090b821b55399fbc41", "archive_sha256": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"}, {"url": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "97db47353db76326b874589a5ad0a04501cc74cd72e237e7bd956e7472c41f1f", "archive_sha256": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"}, {"url": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "d0a2549a532f65299aea5599ee1bedffe47101a07d0de21bec07068547ae237e", "archive_sha256": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"}, {"url": "/docs/16/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 16.15 \u00b7 using-explain", "sha256": "bd8b86e5281cf0e52ad6e0e4bb8b6ff6510dac61982b44f0c1dd07d54012db3c"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel", "Async"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "17": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "dbf4227a43dd8570fd4ff6fc12312a0e7e96f1e9f79b35b46204fbe01d483188", "archive_sha256": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979"}, {"url": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "10f9875b7384fddcd0750b41f7357933769a840c57a7bc0e29eecd4cdc5b8f4c", "archive_sha256": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=17", "label": "EXPLAIN"}, {"url": "/docs/17/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/17/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=17", "label": "work_mem"}], "release": {"ref": "PostgreSQL 17.11 source archive", "label": "17.11", "major": "17", "channel": "stable", "revision": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979", "source_url": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "line": 1433, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1433", "sha256": "741251b1a3b6d269a52a673d42eb63b02e13a5872db7b359b137086ab21b63c8", "archive_sha256": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979"}, {"url": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "line": 201, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:201", "sha256": "a77576e158b94cb01fa8c5174ba133004eabdd727660323f8afc66c8d2e757b8", "archive_sha256": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979"}, {"url": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "dbf4227a43dd8570fd4ff6fc12312a0e7e96f1e9f79b35b46204fbe01d483188", "archive_sha256": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979"}, {"url": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "d390dd69e2d3f5085beb42b33e46ff0676a2959b916a12b82118a7e545f8e562", "archive_sha256": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979"}, {"url": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "10f9875b7384fddcd0750b41f7357933769a840c57a7bc0e29eecd4cdc5b8f4c", "archive_sha256": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979"}, {"url": "/docs/17/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 17.11 \u00b7 using-explain", "sha256": "8e3422c77496cc53bfc225ccadda3e82eb23c8c362b8eb95e7fb02cdb315ea78"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel", "Async"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "18": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "81e2aeb0cc0d4cece84b7514385636cd11ea0e1faab93c721d4c3b86c20c9104", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "e2453b7155d55db8c3a59bc929362f01d3f9692b0a483e5aa81a7b6c50db6102", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=18", "label": "EXPLAIN"}, {"url": "/docs/18/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/18/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=18", "label": "work_mem"}], "release": {"ref": "PostgreSQL 18.6 source archive", "label": "18.6", "major": "18", "channel": "stable", "revision": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f", "source_url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "line": 1418, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1418", "sha256": "34c86d6070224a0e981efef51f79101d6d505e5874f1684ace183034bab14bb4", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "line": 201, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:201", "sha256": "f8a06a3f539077249b20664b2812433db6d7bd12b2c0ca633525db43d06f112a", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "81e2aeb0cc0d4cece84b7514385636cd11ea0e1faab93c721d4c3b86c20c9104", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "52422b327a8049fbbb20d8b96008a0fc0a6fafa60f7eff3c695d5b2e83830120", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "e2453b7155d55db8c3a59bc929362f01d3f9692b0a483e5aa81a7b6c50db6102", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "/docs/18/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 18.6 \u00b7 using-explain", "sha256": "60040c30180093418a0affe56dd27dff9df2504b705b38039589e458bf5c31ed"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel", "Async"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "19": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "14f9eed6e8f71de94c064f7265c0724022326d6acf2ab4d2da6d17ccbd206188", "archive_sha256": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86"}, {"url": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "3394cc4f8c9e397b78f6b0d99fba931fd809450ec7b5ff051798ecbd0dcf3b32", "archive_sha256": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=19", "label": "EXPLAIN"}, {"url": "/docs/19/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/19/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=19", "label": "work_mem"}], "release": {"ref": "PostgreSQL 19beta4 source archive", "label": "19beta4", "major": "19", "channel": "preview", "revision": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86", "source_url": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "line": 1430, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1430", "sha256": "8b115b1c194a4b54ae630209a741e293b1df49a9052f10b2de9ca092a48998e3", "archive_sha256": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86"}, {"url": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "line": 201, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:201", "sha256": "5e39b2037bed672da55104229ecc32da5abde44c26bcad01479edcfa044d09ed", "archive_sha256": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86"}, {"url": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "14f9eed6e8f71de94c064f7265c0724022326d6acf2ab4d2da6d17ccbd206188", "archive_sha256": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86"}, {"url": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "1c65d5d6b6c81c71531685843647869bcae630779d815a5036b06e070c6c06c7", "archive_sha256": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86"}, {"url": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "3394cc4f8c9e397b78f6b0d99fba931fd809450ec7b5ff051798ecbd0dcf3b32", "archive_sha256": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86"}, {"url": "/docs/19/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 19beta4 \u00b7 using-explain", "sha256": "52f111fbd213e2200146319d01a9dcc2ea90001617d2a28edc52f7954c2dd70b"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel", "Async"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "20": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "4534aeb178af033afae2e3fbccd9318785fb6869e553e697b0bf73e1fe5b3798", "archive_sha256": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41"}, {"url": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "3394cc4f8c9e397b78f6b0d99fba931fd809450ec7b5ff051798ecbd0dcf3b32", "archive_sha256": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=20", "label": "EXPLAIN"}, {"url": "/docs/devel/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/devel/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=20", "label": "work_mem"}], "release": {"ref": "PostgreSQL 20devel source archive", "label": "20devel", "major": "20", "channel": "devel", "revision": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41", "source_url": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "source_snapshot_utc": "26-Sep-2026 20:22"}, "sources": [{"url": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "line": 1430, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1430", "sha256": "13402758013520451539427b5993db06d463ca11c4e2d4cc5444e82367688077", "archive_sha256": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41"}, {"url": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "line": 201, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:201", "sha256": "5e39b2037bed672da55104229ecc32da5abde44c26bcad01479edcfa044d09ed", "archive_sha256": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41"}, {"url": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "4534aeb178af033afae2e3fbccd9318785fb6869e553e697b0bf73e1fe5b3798", "archive_sha256": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41"}, {"url": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "7a94ed1652f0d74d50c39971d1cd3e8051dbc0d6058f31b6de71a433ca343521", "archive_sha256": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41"}, {"url": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "3394cc4f8c9e397b78f6b0d99fba931fd809450ec7b5ff051798ecbd0dcf3b32", "archive_sha256": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41"}, {"url": "/docs/devel/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 20devel \u00b7 using-explain", "sha256": "99cfea3035876ea63f88b75ba8c964b51a32a70606544e09f769c0b60a234b31"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel", "Async"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}}}, "snapshot": {"facts": [{"label": "Core node tag", "value": "T_BitmapOr"}, {"label": "Structured EXPLAIN Node Type", "value": "BitmapOr"}, {"label": "Inputs", "value": "Bitmap-producing child plans"}, {"label": "Output", "value": "Tuple-location bitmap, not a tuple stream"}, {"label": "Executor initializer", "value": "ExecInitBitmapOr"}, {"label": "Memory mechanism", "value": "bitmap-lossification"}], "memory": {"evidence": [{"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "81e2aeb0cc0d4cece84b7514385636cd11ea0e1faab93c721d4c3b86c20c9104", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "e2453b7155d55db8c3a59bc929362f01d3f9692b0a483e5aa81a7b6c50db6102", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}], "mechanism": "bitmap-lossification", "description": "The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary.", "source_notes": []}, "tables": [{"key": "explain-labels", "rows": [{"label": "BitmapOr", "identity": "BitmapOr"}], "title": "EXPLAIN labels in this source build", "columns": [{"key": "label", "label": "Text-format label"}, {"key": "identity", "label": "Structured node identity"}]}], "related": [{"url": "/wiki/sql/explain/?v=18", "label": "EXPLAIN"}, {"url": "/docs/18/using-explain.html", "label": "Using EXPLAIN"}, {"url": "/docs/18/parallel-plans.html", "label": "Parallel plans"}, {"url": "/wiki/guc/work_mem/?v=18", "label": "work_mem"}], "release": {"ref": "PostgreSQL 18.6 source archive", "label": "18.6", "major": "18", "channel": "stable", "revision": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f", "source_url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "source_snapshot_utc": ""}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "line": 1418, "path": "src/backend/commands/explain.c", "label": "src/backend/commands/explain.c:1418", "sha256": "34c86d6070224a0e981efef51f79101d6d505e5874f1684ace183034bab14bb4", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "line": 201, "path": "src/backend/executor/execProcnode.c", "label": "src/backend/executor/execProcnode.c:201", "sha256": "f8a06a3f539077249b20664b2812433db6d7bd12b2c0ca633525db43d06f112a", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/backend/executor/nodeBitmapOr.c", "label": "src/backend/executor/nodeBitmapOr.c", "sha256": "81e2aeb0cc0d4cece84b7514385636cd11ea0e1faab93c721d4c3b86c20c9104", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/include/nodes/plannodes.h", "label": "src/include/nodes/plannodes.h", "sha256": "52422b327a8049fbbb20d8b96008a0fc0a6fafa60f7eff3c695d5b2e83830120", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "path": "src/backend/nodes/tidbitmap.c", "label": "src/backend/nodes/tidbitmap.c", "sha256": "e2453b7155d55db8c3a59bc929362f01d3f9692b0a483e5aa81a7b6c50db6102", "archive_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "/docs/18/using-explain.html#USING-EXPLAIN-CAVEATS", "path": "using-explain.html", "label": "PostgreSQL 18.6 \u00b7 using-explain", "sha256": "60040c30180093418a0affe56dd27dff9df2504b705b38039589e458bf5c31ed"}], "node_tag": "T_BitmapOr", "sections": [{"title": "EXPLAIN names and attributes", "paragraphs": ["Structured formats use the Node Type above. Text-format spellings can also include operation, strategy, join type, scan direction or aggregation-stage attributes.", "Text names recorded by this source: BitmapOr.", "Parallel-aware and parallel-safe are different plan properties. A node running inside a parallel worker is not necessarily a parallel-aware node."]}, {"title": "Memory and temporary storage", "paragraphs": ["The node allocates a tuple-location bitmap using a work_mem-derived budget. A bitmap can retain page-level lossy entries instead of every tuple location; heap rechecks then remain necessary."]}, {"title": "Parallel execution and instrumentation", "paragraphs": ["The source callbacks below can coordinate execution or collect worker instrumentation. Their presence is not a blanket claim that this node supports a shared parallel scan or shared state.", "Callbacks in this build: none extracted from this node implementation."]}, {"title": "Same-version manual discussion", "paragraphs": ["BitmapAnd and BitmapOr nodes always report their actual row counts as zero, due to implementation limitations."]}, {"title": "Executor implementation notes", "paragraphs": ["NOTES BitmapOr nodes don't make use of their left and right subtrees, rather they maintain a list of subplans, much like Append nodes. The logic is much simpler than Append, however, since we needn't cope with forward/backward execution.", "call ExecInitNode on each of the plans to be executed and save the results into the array \"bitmapplanstates\".", "BitmapOr plans don't have expression contexts because they never call ExecQual or ExecProject. They don't need any tuple slots either.", "We can special-case BitmapIndexScan children to avoid an explicit tbm_union step for each child: just pass down the current result bitmap and let the child OR directly into it.", "ExecReScan doesn't know about my subplans, so I have to do changed-parameter signaling myself."]}, {"code": "case T_BitmapOr:\n\t\t\tpname = sname = \"BitmapOr\";\n\t\t\tbreak;", "title": "EXPLAIN identity in core source"}], "strategies": [], "description": ["Unions bitmaps produced by its child plans."], "evidence_kind": "source and documentation", "explain_names": ["BitmapOr"], "partial_modes": [], "comparison_data": {"node_tag": "T_BitmapOr", "strategies": [], "text_names": ["BitmapOr"], "initializer": "ExecInitBitmapOr", "partial_modes": [], "memory_mechanism": "bitmap-lossification", "parallel_callbacks": []}, "comparison_hash": "c0ca503a6029c37ec720213dcdc3094997eb194d4920da68f94a7420d3e8f1d2", "explain_prefixes": ["Parallel", "Async"], "runtime_verified": false, "source_inventory": {"explain": "src/backend/commands/explain.c", "executor": "src/backend/executor/execProcnode.c", "implementation": "src/backend/executor/nodeBitmapOr.c"}, "parallel_callbacks": []}, "comparison": {"left": "17", "right": "18", "status": "unchanged", "diff": ""}}