Home Database Mysql Tutorial PostgreSQL 9.4版本的物化视图更新

PostgreSQL 9.4版本的物化视图更新

Jun 07, 2016 pm 04:00 PM

PostgreSQL的9.4版本出来有一段时间了,也更新了很多内容,其中之一是比较感兴趣的物化视图的更新,对比原先的物化视图语法,新增

PostgreSQL的9.4版本出来有一段时间了,也更新了很多内容,其中之一是比较感兴趣的物化视图的更新,对比原先的物化视图语法,新增了一个CONCURRENTLY参数。

 一、新语法:

--创建语法,未有更新 CREATE MATERIALIZED VIEW table_name [ (column_name [, ...] ) ] [ WITH ( storage_parameter [= value] [, ... ] ) ] [ TABLESPACE tablespace_name ] AS query [ WITH [ NO ] DATA ] --刷新语法 REFRESH MATERIALIZED VIEW [ CONCURRENTLY ] name [ WITH [ NO ] DATA ]

二、数据准备:

[postgres@ ~]$ psql psql (9.4.1) Type "help" for help. postgres=# create table tbl_kenyon(id int,remark text); CREATE TABLE postgres=# insert into tbl_kenyon select generate_series(1,1000000),md5(random()::text); INSERT 0 1000000 postgres=# select * from tbl_kenyon limit 10; id | remark ----+---------------------------------- 1 | d4fc1c7440a4d1672028586c2bb76514 2 | 5c1590519fa47f02db2895146a5f62a4 3 | 1710ac4199746e9bfa188f1655d1f857 4 | 6cae64191c2bc309a4884301e77b26ad 5 | 813987a5c3af2d75bd0de6e288083b10 6 | c52baa42cda22c89719bfb59dde1f78b 7 | 491003337ea4e887c5ac24d174c691c6 8 | 455cdf32b170fcf2b450c0b974fbf310 9 | 43adb30aeb0a21ab35fdf97064ad1d21 10 | 97dc1adc5484244a077e87ef36ecfe09 (10 rows) --创建简单的物化视图 postgres=# create materialized view mv_tbl_kenyon as select * from tbl_kenyon ; SELECT 1000000 postgres=# \d+ List of relations Schema | Name | Type | Owner | Size | Description --------+---------------+-------------------+----------+-------+------------- public | mv_tbl_kenyon | materialized view | postgres | 65 MB | public | tbl_kenyon | table | postgres | 65 MB | (2 rows)

三、测试用例:

--测试不带concurrently postgres=# insert into tbl_kenyon values(1000001,md5(random()::text)); INSERT 0 1 postgres=# select max(id) from mv_tbl_kenyon ; max --------- 1000000 (1 row) postgres=# \timing Timing is on. postgres=# refresh materialized view mv_tbl_kenyon ; REFRESH MATERIALIZED VIEW Time: 2056.460 ms --测试带concurrently,需要建一个唯一索引 postgres=# insert into tbl_kenyon values(1000002,md5(random()::text)); INSERT 0 1 Time: 9.434 ms postgres=# refresh materialized view concurrently mv_tbl_kenyon; ERROR: cannot refresh materialized view "public.mv_tbl_kenyon" concurrently HINT: Create a unique index with no WHERE clause on one or more columns of the materialized view. Time: 22109.877 ms postgres=# create unique index idx_ken on mv_tbl_kenyon(id); CREATE INDEX Time: 707.721 ms postgres=# select max(id) from mv_tbl_kenyon ; max --------- 1000001 (1 row) Time: 1.110 ms postgres=# begin; BEGIN postgres=# refresh materialized view concurrently mv_tbl_kenyon; REFRESH MATERIALIZED VIEW Time: 24674.739 ms --如果在refresh的时候,前面加个begin; --还能发现在开启的另外的session里面,是不会阻塞查询的,反之不加concurrently会阻塞 postgres=# select * from mv_tbl_kenyon limit 10; id | remark ----+---------------------------------- 1 | d4fc1c7440a4d1672028586c2bb76514 2 | 5c1590519fa47f02db2895146a5f62a4 3 | 1710ac4199746e9bfa188f1655d1f857 4 | 6cae64191c2bc309a4884301e77b26ad 5 | 813987a5c3af2d75bd0de6e288083b10 6 | c52baa42cda22c89719bfb59dde1f78b 7 | 491003337ea4e887c5ac24d174c691c6 8 | 455cdf32b170fcf2b450c0b974fbf310 9 | 43adb30aeb0a21ab35fdf97064ad1d21 10 | 97dc1adc5484244a077e87ef36ecfe09 (10 rows)

四、源码
 相关唯一索引的源码,在matview.c里面可以查看:

--先初始化唯一索引是false foundUniqueIndex = false; --如果找到唯一索引赋值为true if (foundUniqueIndex) appendStringInfoString(&querybuf, " AND "); colname = quote_identifier(NameStr((tupdesc->attrs[attnum - 1])->attname)); appendStringInfo(&querybuf, "newdata.%s ", colname); type = attnumTypeId(matviewRel, attnum); op = lookup_type_cache(type, TYPECACHE_EQ_OPR)->eq_opr; mv_GenerateOper(&querybuf, op); appendStringInfo(&querybuf, " mv.%s", colname); foundUniqueIndex = true; --如果找不到唯一索引报error if (!foundUniqueIndex) ereport(ERROR,(errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE), errmsg("cannot refresh materialized view \"%s\" concurrently",matviewname), errhint("Create a unique index with no WHERE clause on one or more columns of the materialized view."))); appendStringInfoString(&querybuf, " AND newdata OPERATOR(pg_catalog.*=) mv) " "WHERE newdata IS NULL OR mv IS NULL " "ORDER BY tid");

五、总结:
1.新版的物化视图新增了concurrently参数,可以使在刷新视图时不会锁住该物化视图的查询工作
2.该参数的原理和优缺点与索引的concurrently类似,以时间来换取查询锁,,刷新的速度会变得很慢
3.增量刷新的参数还没有,比较遗憾

------------------------------------华丽丽的分割线------------------------------------

CentOS 6.3环境下yum安装PostgreSQL 9.3

PostgreSQL缓存详述

Windows平台编译 PostgreSQL

Ubuntu下LAPP(Linux+Apache+PostgreSQL+PHP)环境的配置与安装

Ubuntu上的phppgAdmin安装及配置

CentOS平台下安装PostgreSQL9.3

PostgreSQL配置Streaming Replication集群

如何在CentOS 7/6.5/6.4 下安装PostgreSQL 9.3 与 phpPgAdmin 

------------------------------------华丽丽的分割线------------------------------------

PostgreSQL 的详细介绍:请点这里
PostgreSQL 的下载地址:请点这里

本文永久更新链接地址

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

When might a full table scan be faster than using an index in MySQL? When might a full table scan be faster than using an index in MySQL? Apr 09, 2025 am 12:05 AM

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Explain InnoDB Full-Text Search capabilities. Explain InnoDB Full-Text Search capabilities. Apr 02, 2025 pm 06:09 PM

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

Can I install mysql on Windows 7 Can I install mysql on Windows 7 Apr 08, 2025 pm 03:21 PM

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

MySQL: Simple Concepts for Easy Learning MySQL: Simple Concepts for Easy Learning Apr 10, 2025 am 09:29 AM

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

Difference between clustered index and non-clustered index (secondary index) in InnoDB. Difference between clustered index and non-clustered index (secondary index) in InnoDB. Apr 02, 2025 pm 06:25 PM

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values ​​and pointers to data rows, and is suitable for non-primary key column queries.

The relationship between mysql user and database The relationship between mysql user and database Apr 08, 2025 pm 07:15 PM

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

Can mysql and mariadb coexist Can mysql and mariadb coexist Apr 08, 2025 pm 02:27 PM

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial). Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial). Apr 02, 2025 pm 07:05 PM

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.

See all articles