PostgresChina 2018 张启程 为什么我们抛弃MongoDB和MySQL,选择PgSQL甚至连运维人员都没有!而我们的业务又必须保障绝对稳 定,经过反复尝试,我们放弃了自建数据库的方式(坑太 多!填不完) • 目前所有业务全部使用阿里云的PgSQL,针对不同客户的业 务量大小,选择不同配置的数据库,开通简单,拓展扩容 方便。我们的客户也不需要太专业的运维人员就可以直接 使用,(稳如死狗!) Thanks0 码力 | 9 页 | 563.82 KB | 1 年前3
阿里云 AnalyticDB for PostgreSQL
- 打造更简单易用的Cloud SQL Data Warehouse批量同步 1 3 4 2 云化在线数仓 : 简化、敏捷、一栈式构筑数据仓库 • 一键实现 十分钟 集群创建部署 • 图形化实例管理及自动监控报警 实例SQL安全审计 实例实时监控 实例配置信息 • 云上多种生态工具配套: DTS数据传输 QuickBI DataV 数据集成 阿里云数据工 具服务 阿里云第三方 服务 … … Kettel 客户案例 – 阿里妈妈数据银行广告业务0 码力 | 22 页 | 2.98 MB | 1 年前3
postgresql操作手册postgres:postgres /data_pg # vi /var/lib/pgsql/data/postgresql.conf #pg-10版本,添加或修改以下配置 data_directory = '/data_pg/data/' # mv /var/lib/pgsql/* /data_pg/ #将原数据目录下所有内容移动到新数0 码力 | 17 页 | 445.84 KB | 1 年前3
PostgreSQL 9.0 Documentation[ boolean ] VERBOSE [ boolean ] COSTS [ boolean ] BUFFERS [ boolean ] FORMAT { TEXT | XML | JSON | YAML } Description This command displays the execution plan that the PostgreSQL planner generates for parameter. It defaults to FALSE. FORMAT Specify the output format, which can be TEXT, XML, JSON, or YAML. Non-text output contains the same information as the text output format, but is easier for programs .5.98 rows=1 width=4) Index Cond: (i = 4) (2 rows) Here is the same query, but in YAML output: EXPLAIN (FORMAT YAML) SELECT * FROM foo WHERE i=’4’; QUERY PLAN ------------------------------- - Plan:0 码力 | 2561 页 | 5.55 MB | 1 年前3
PostgreSQL 9.0 Documentation[ boolean ] VERBOSE [ boolean ] COSTS [ boolean ] BUFFERS [ boolean ] FORMAT { TEXT | XML | JSON | YAML } Description This command displays the execution plan that the PostgreSQL planner generates for parameter. It defaults to FALSE. FORMAT Specify the output format, which can be TEXT, XML, JSON, or YAML. Non-text output con- tains the same information as the text output format, but is easier for programs rows=1 width=4) Index Cond: (i = 4) (2 rows) Here is the same query, but in YAML output: 1240 EXPLAIN EXPLAIN (FORMAT YAML) SELECT * FROM foo WHERE i=’4’; QUERY PLAN ------------------------------- -0 码力 | 2401 页 | 5.50 MB | 1 年前3
PostgreSQL 9.2 Documentationprogram for further analysis, you should use one of its machine-readable output formats (XML, JSON, or YAML) instead. 14.1.1. EXPLAIN Basics The structure of a query plan is a tree of plan nodes. Nodes at [ boolean ] COSTS [ boolean ] BUFFERS [ boolean ] TIMING [ boolean ] FORMAT { TEXT | XML | JSON | YAML } Description This command displays the execution plan that the PostgreSQL planner generates for enabled. It defaults to TRUE. FORMAT Specify the output format, which can be TEXT, XML, JSON, or YAML. Non-text output con- tains the same information as the text output format, but is easier for programs0 码力 | 2829 页 | 7.02 MB | 1 年前3
PostgreSQL 9.2 Documentationprogram for further analysis, you should use one of its machine-readable output formats (XML, JSON, or YAML) instead. 14.1.1. EXPLAIN Basics The structure of a query plan is a tree of plan nodes. Nodes at [ boolean ] COSTS [ boolean ] BUFFERS [ boolean ] TIMING [ boolean ] FORMAT { TEXT | XML | JSON | YAML } Description This command displays the execution plan that the PostgreSQL planner generates for enabled. It defaults to TRUE. FORMAT Specify the output format, which can be TEXT, XML, JSON, or YAML. Non-text output contains the same information as the text output format, but is easier for programs0 码力 | 3007 页 | 7.07 MB | 1 年前3
PostgreSQL 9.3.25 Documentationprogram for further analysis, you should use one of its machine-readable output formats (XML, JSON, or YAML) instead. 14.1.1. EXPLAIN Basics The structure of a query plan is a tree of plan nodes. Nodes at [ boolean ] COSTS [ boolean ] BUFFERS [ boolean ] TIMING [ boolean ] FORMAT { TEXT | XML | JSON | YAML } Description This command displays the execution plan that the PostgreSQL planner generates for enabled. It defaults to TRUE. FORMAT Specify the output format, which can be TEXT, XML, JSON, or YAML. Non-text output con- tains the same information as the text output format, but is easier for programs0 码力 | 3002 页 | 7.47 MB | 1 年前3
PostgreSQL 9.3 Documentationprogram for further analysis, you should use one of its machine-readable output formats (XML, JSON, or YAML) instead. 14.1.1. EXPLAIN Basics The structure of a query plan is a tree of plan nodes. Nodes at [ boolean ] COSTS [ boolean ] BUFFERS [ boolean ] TIMING [ boolean ] FORMAT { TEXT | XML | JSON | YAML } Description This command displays the execution plan that the PostgreSQL planner generates for defaults to TRUE. 1575 EXPLAIN FORMAT Specify the output format, which can be TEXT, XML, JSON, or YAML. Non-text output contains the same information as the text output format, but is easier for programs0 码力 | 3183 页 | 7.53 MB | 1 年前3
PostgreSQL 9.1.24 Documentation
[ boolean ] VERBOSE [ boolean ] COSTS [ boolean ] BUFFERS [ boolean ] FORMAT { TEXT | XML | JSON | YAML } Description This command displays the execution plan that the PostgreSQL planner generates for parameter. It defaults to FALSE. FORMAT Specify the output format, which can be TEXT, XML, JSON, or YAML. Non-text output con- tains the same information as the text output format, but is easier for programs rows=1 width=4) Index Cond: (i = 4) (2 rows) Here is the same query, but in YAML output: 1376 EXPLAIN EXPLAIN (FORMAT YAML) SELECT * FROM foo WHERE i=’4’; QUERY PLAN ------------------------------- -0 码力 | 2667 页 | 6.57 MB | 1 年前3
共 33 条
- 1
- 2
- 3
- 4













