The Vitess 6.0 DocumentationInspired from the usual SQL sequences (implemented in different ways by Oracle, SQL Server and PostgreSQL). • Very high throughput for ID creation, using a configurable in-memory block allocation. • Topology service should be used only for passive discovery. 166 • Support for PostgreSQL: Vitess should be able to support PostgreSQL for both storing data, and speaking the protocol in VTGate. Troubleshoot0 码力 | 210 页 | 846.79 KB | 1 年前3- The Vitess 5.0 DocumentationInspired from the usual SQL sequences (implemented in different ways by Oracle, SQL Server and PostgreSQL). • Very high throughput for ID creation, using a configurable in-memory block allocation. • Topology service should be used only for passive discovery. • Support for PostgreSQL: Vitess should be able to support PostgreSQL for both storing data, and speaking the protocol in VTGate. Troubleshoot0 码力 | 206 页 | 875.06 KB | 1 年前3
- The Vitess 7.0 DocumentationInspired from the usual SQL sequences (implemented in different ways by Oracle, SQL Server and PostgreSQL). • Very high throughput for ID creation, using a configurable in-memory block allocation. • Topology service should be used only for passive discovery. • Support for PostgreSQL: Vitess should be able to support PostgreSQL for both storing data, and speaking the protocol in VTGate. Troubleshoot0 码力 | 254 页 | 949.63 KB | 1 年前3
- The Vitess 8.0 DocumentationInspired from the usual SQL sequences (implemented in different ways by Oracle, SQL Server and PostgreSQL). • Very high throughput for ID creation, using a configurable in-memory block allocation. • Topology service should be used only for passive discovery. • Support for PostgreSQL: Vitess should be able to support PostgreSQL for both storing data, and speaking the protocol in VTGate. Troubleshoot0 码力 | 331 页 | 1.35 MB | 1 年前3
- The Vitess 9.0 DocumentationInspired from the usual SQL sequences (implemented in different ways by Oracle, SQL Server and PostgreSQL). • Very high throughput for ID creation, using a configurable in-memory block allocation. • Topology service should be used only for passive discovery. • Support for PostgreSQL: Vitess should be able to support PostgreSQL for both storing data, and speaking the protocol in VTGate. Troubleshoot0 码力 | 417 页 | 2.96 MB | 1 年前3
- The Vitess 10.0 Documentation
Inspired from the usual SQL sequences (implemented in different ways by Oracle, SQL Server and PostgreSQL). • Very high throughput for ID creation, using a configurable in-memory block allocation. • Topology service should be used only for passive discovery. • Support for PostgreSQL: Vitess should be able to support PostgreSQL for both storing data, and speaking the protocol in VTGate. Troubleshoot0 码力 | 455 页 | 3.07 MB | 1 年前3
- The Vitess 11.0 DocumentationInspired from the usual SQL sequences (implemented in different ways by Oracle, SQL Server and PostgreSQL). • Very high throughput for ID creation, using a configurable in-memory block allocation. •0 码力 | 481 页 | 3.14 MB | 1 年前3
- The Vitess 12.0 DocumentationInspired from the usual SQL sequences (implemented in different ways by Oracle, SQL Server and PostgreSQL). • Very high throughput for ID creation, using a configurable in-memory block allocation. •0 码力 | 534 页 | 3.32 MB | 1 年前3
共 8 条
- 1