 The Vitess 12.0 Documentation. . . . . . . . . . . . . 64 What happens when a Reshard is cutover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 What happens when a MoveTables workflow is cutover but in doing so you might be able to utilitize additional or newer hardware which has more headroom before you need to perform additional operations such as sharding. Similarly, tables that are updated at If we try a more complicated query that requires data from MySQL, VTGate will rewrite the query before sending it down. If we were to write something like: WHERE col = @my_user_variable What MySQL will0 码力 | 534 页 | 3.32 MB | 1 年前3 The Vitess 12.0 Documentation. . . . . . . . . . . . . 64 What happens when a Reshard is cutover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 What happens when a MoveTables workflow is cutover but in doing so you might be able to utilitize additional or newer hardware which has more headroom before you need to perform additional operations such as sharding. Similarly, tables that are updated at If we try a more complicated query that requires data from MySQL, VTGate will rewrite the query before sending it down. If we were to write something like: WHERE col = @my_user_variable What MySQL will0 码力 | 534 页 | 3.32 MB | 1 年前3
 The Vitess 5.0 DocumentationTypes See the user guide VTTablet Modes for more information. • master - A replica tablet that happens to currently be the MySQL master for its shard. • replica - A MySQL slave that is eligible to be driver, the PHP PDO driver or VTGate v3 improvements. We’re looking forward to any contribution! Before you start larger contributions, make sure to reach out first and discuss your plans with us. This The Go Programming Language Specification is also useful as a reference guide. Learning Vitess Before diving into the Vitess codebase, make yourself familiar with the system and run it yourself: • Read0 码力 | 206 页 | 875.06 KB | 1 年前3 The Vitess 5.0 DocumentationTypes See the user guide VTTablet Modes for more information. • master - A replica tablet that happens to currently be the MySQL master for its shard. • replica - A MySQL slave that is eligible to be driver, the PHP PDO driver or VTGate v3 improvements. We’re looking forward to any contribution! Before you start larger contributions, make sure to reach out first and discuss your plans with us. This The Go Programming Language Specification is also useful as a reference guide. Learning Vitess Before diving into the Vitess codebase, make yourself familiar with the system and run it yourself: • Read0 码力 | 206 页 | 875.06 KB | 1 年前3
 PostgreSQL 14.10 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 2871 页 | 13.38 MB | 1 年前3 PostgreSQL 14.10 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 2871 页 | 13.38 MB | 1 年前3
 The Vitess 6.0 Documentationmove, but in doing so you might also be able to migrate to newer hardware which has more headroom before you need to perform additional operations such as sharding. Similarly, tables that are updated at Types See the user guide VTTablet Modes for more information. • master - A replica tablet that happens to currently be the MySQL master for its shard. • replica - A MySQL slave that is eligible to be driver, the PHP PDO driver or VTGate v3 improvements. We’re looking forward to any contribution! Before you start larger contributions, make sure to reach out first and discuss your plans with us. This0 码力 | 210 页 | 846.79 KB | 1 年前3 The Vitess 6.0 Documentationmove, but in doing so you might also be able to migrate to newer hardware which has more headroom before you need to perform additional operations such as sharding. Similarly, tables that are updated at Types See the user guide VTTablet Modes for more information. • master - A replica tablet that happens to currently be the MySQL master for its shard. • replica - A MySQL slave that is eligible to be driver, the PHP PDO driver or VTGate v3 improvements. We’re looking forward to any contribution! Before you start larger contributions, make sure to reach out first and discuss your plans with us. This0 码力 | 210 页 | 846.79 KB | 1 年前3
 PostgreSQL 14.10 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 3032 页 | 13.27 MB | 1 年前3 PostgreSQL 14.10 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 3032 页 | 13.27 MB | 1 年前3
 The Vitess 7.0 Documentationmove, but in doing so you might also be able to migrate to newer hardware which has more headroom before you need to perform additional operations such as sharding. Similarly, tables that are updated at Types See the user guide VTTablet Modes for more information. • master - A replica tablet that happens to currently be the MySQL master for its shard. • replica - A MySQL replica that is eligible to be driver, the PHP PDO driver or VTGate v3 improvements. We’re looking forward to any contribution! Before you start larger contributions, make sure to reach out first and discuss your plans with us. This0 码力 | 254 页 | 949.63 KB | 1 年前3 The Vitess 7.0 Documentationmove, but in doing so you might also be able to migrate to newer hardware which has more headroom before you need to perform additional operations such as sharding. Similarly, tables that are updated at Types See the user guide VTTablet Modes for more information. • master - A replica tablet that happens to currently be the MySQL master for its shard. • replica - A MySQL replica that is eligible to be driver, the PHP PDO driver or VTGate v3 improvements. We’re looking forward to any contribution! Before you start larger contributions, make sure to reach out first and discuss your plans with us. This0 码力 | 254 页 | 949.63 KB | 1 年前3
 PostgreSQL 17beta1 A4 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 3017 页 | 14.45 MB | 1 年前3 PostgreSQL 17beta1 A4 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 3017 页 | 14.45 MB | 1 年前3
 PostgreSQL 17beta1 US Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 3188 页 | 14.32 MB | 1 年前3 PostgreSQL 17beta1 US Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 3188 页 | 14.32 MB | 1 年前3
 PostgreSQL 16.1 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 2974 页 | 14.22 MB | 1 年前3 PostgreSQL 16.1 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 2974 页 | 14.22 MB | 1 年前3
 PostgreSQL 13.13 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 2782 页 | 13.00 MB | 1 年前3 PostgreSQL 13.13 Documentationhappen that we tell you to update to a newer version to see if the bug happens there. Or we might decide that the bug cannot be fixed before some major rewrite we might be planning is done. Or perhaps it is need help immediately, consider obtaining a commercial support contract. 5.1. Identifying Bugs Before you report a bug, please read and re-read the documentation to verify that you can really do whatever not necessarily a bug either, unless compliance for the specific feature is explicitly claimed. Before you continue, check on the TODO list and in the FAQ to see if your bug is already known. If you cannot0 码力 | 2782 页 | 13.00 MB | 1 年前3
共 239 条
- 1
- 2
- 3
- 4
- 5
- 6
- 24














