* table_index_build_scan - scan the table to find tuples to be indexed * * This is called back from an access-method-specific index build procedure * after the AM has done whatever setup it needs. The parent table relation * is scanned to find tuples that should be entered into the index. Each * such tuple is passed to the AM's callback routine, which does the right * things to add it to t
| 2019 | * for other AMs later. |
| 2020 | */ |
| 2021 | static inline double |
| 2022 | table_index_build_scan(Relation table_rel, |
| 2023 | Relation index_rel, |
| 2024 | struct IndexInfo *index_info, |
| 2025 | bool allow_sync, |
| 2026 | bool progress, |
| 2027 | IndexBuildCallback callback, |
| 2028 | void *callback_state, |
| 2029 | TableScanDesc scan) |
| 2030 | { |
| 2031 | return table_rel->rd_tableam->index_build_range_scan(table_rel, |
| 2032 | index_rel, |
| 2033 | index_info, |
| 2034 | allow_sync, |
| 2035 | false, |
| 2036 | progress, |
| 2037 | 0, |
| 2038 | InvalidBlockNumber, |
| 2039 | callback, |
| 2040 | callback_state, |
| 2041 | scan); |
| 2042 | } |
| 2043 | |
| 2044 | /* |
| 2045 | * As table_index_build_scan(), except that instead of scanning the complete |
no outgoing calls
no test coverage detected