PostgreSQL 查询优化器解析OpenPie. All rights reserved. OpenPie Confidential • About OpenPie and Me • What Does Planner Do? • Phases of Planning Agenda @2024 OpenPie. All rights reserved. OpenPie Confidential @2024 OpenPie. All reserved. OpenPie Confidential @2024 OpenPie. All rights reserved. OpenPie Confidential Part Three: Phases of Planning @2024 OpenPie. All rights reserved. OpenPie Confidential • Preprocessing ØSimplify steps that are not scans or joins • Postprocessing ØConvert results into form the executor wants Phases of Planning @2024 OpenPie. All rights reserved. OpenPie Confidential • Simplify scalar expressions0 码力 | 37 页 | 851.23 KB | 1 年前3
Pentest-Report Vitess 02.2019revealed a rather limited attack surface. This observation was later confirmed as the subsequent phases of the test ensued. While the results of this assessment are few and far between and may suggest defines the scope of the test and then moves on to explaining the employed test methodology. Subsequent phases and details relevant for the test are covered next and clarify which aspects were investigated during that was used during this source code audit and penetration tests. The test was divided into two phases. Each phase had goals that were closely linked to the areas in scope. The initial phase (Phase 1)0 码力 | 9 页 | 155.02 KB | 1 年前3
VMware Greenplum 7 DocumentationHeap Table Cluster Phases 941 AO/CO Table Cluster Phases 942 COPY Progress Reporting 942 CREATE INDEX Progress Reporting 943 VACUUM Progress Reporting 944 Heap Table Vacuum Phases 944 AO/CO Table Vacuum Vacuum Phases 945 Base Backup Progress Reporting 945 Example: Viewing Real-Time Command Progress 946 Additional Considerations 946 Routine System Maintenance Tasks 946 Routine Vacuum and Analyze 947 VMware Greenplum 7 Documentation VMware by Broadcom 940 Greenplum reports progress in phases, where the phases are specific to the command. For example, acquiring sample rows is an analyze progress0 码力 | 2221 页 | 14.19 MB | 1 年前3
The Vitess 6.0 Documentationstores a separate partitioning for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests different ServedFrom record for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service0 码力 | 210 页 | 846.79 KB | 1 年前3
The Vitess 5.0 Documentationstores a separate partitioning for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests different ServedFrom record for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service0 码力 | 206 页 | 875.06 KB | 1 年前3
The Vitess 7.0 Documentationstores a separate partitioning for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests different ServedFrom record for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: 63 • Start with the old topo service implementation we want to replace. • Bring up the new topo0 码力 | 254 页 | 949.63 KB | 1 年前3
The Vitess 11.0 Documentationusing the last vgtid that it received. Architecture/Design During a copy there will two distinct phases: 1. Copy phase: where the vstreamer is sending row data in bulk using the primary key to “paginate” go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service Step T4 is called Fast Forward. Catchup As detailed above the catchup phase runs between two copy phases. During the copy phase the gtid position can move significantly ahead. So we run a replicate till0 码力 | 481 页 | 3.14 MB | 1 年前3
The Vitess 10.0 Documentation
using the last vgtid that it received. Architecture/Design During a copy there will two distinct phases: 1. Copy phase: where the vstreamer is sending row data in bulk using the primary key to “paginate” go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service Step T4 is called Fast Forward. Catchup As detailed above the catchup phase runs between two copy phases. During the copy phase the gtid position can move significantly ahead. So we run a replicate till0 码力 | 455 页 | 3.07 MB | 1 年前3
The Vitess 12.0 DocumentationStep T4 is called Fast Forward. Catchup As detailed above the catchup phase runs between two copy phases. During the copy phase the gtid position can move significantly ahead. So we run a replicate till using the last vgtid that it received. Architecture/Design During a copy there will two distinct phases: 1. Copy phase: where the vstreamer is sending row data in bulk using the primary key to “paginate” go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service0 码力 | 534 页 | 3.32 MB | 1 年前3
TiDB v6.5 Documentationyou can view the progress through the progress bar in the terminal. The restore is divided into two phases, full restore and log restore (restore meta files and restore KV files). After each phase is completed SQL execution phase is in green and other phases are in red on general. If non-green areas are large, it means much database time is consumed in other phases than the execution phase and further cause Time by SQL Type: Mainly are SELECT statements. • Database Time by SQL Phase: Major time-consuming phases are compile in orange and execute in green. Latency in the compile phase is the highest, indicating0 码力 | 5282 页 | 99.69 MB | 1 年前3
共 89 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9













