怎么理解PostgreSQL的PGIndexProperties-創(chuàng)新互聯(lián)

本篇內(nèi)容介紹了“怎么理解PostgreSQL的PG Index Properties”的有關(guān)知識(shí),在實(shí)際案例的操作過程中,不少人都會(huì)遇到這樣的困境,接下來就讓小編帶領(lǐng)大家學(xué)習(xí)一下如何處理這些情況吧!希望大家仔細(xì)閱讀,能夠?qū)W有所成!

專注于為中小企業(yè)提供網(wǎng)站設(shè)計(jì)制作、網(wǎng)站制作服務(wù),電腦端+手機(jī)端+微信端的三站合一,更高效的管理,為中小企業(yè)木蘭免費(fèi)做網(wǎng)站提供優(yōu)質(zhì)的服務(wù)。我們立足成都,凝聚了一批互聯(lián)網(wǎng)行業(yè)人才,有力地推動(dòng)了上1000+企業(yè)的穩(wěn)健成長(zhǎng),幫助中小企業(yè)通過網(wǎng)站建設(shè)實(shí)現(xiàn)規(guī)模擴(kuò)充和轉(zhuǎn)變。

在PostgreSQL 9.6之后,PG提供了三個(gè)函數(shù)來判定Index AM/Index/Index Column是否具備某些屬性,包括pg_indexam_has_property/pg_index_has_property/pg_index_column_has_property.

pg_indexam_has_property
test whether an index access method has a specified property

屬性名稱說明
can_orderDoes the access method support ASC, DESC and related keywords in CREATE INDEX?
can_uniqueDoes the access method support unique indexes?
can_multi_colDoes the access method support indexes with multiple columns?
can_excludeDoes the access method support exclusion constraints?
can_includevDoes the access method support the INCLUDE clause of CREATE INDEX?

下面是本機(jī)AM的查詢結(jié)果,其中heap是堆AM/blackhole_am是先前介紹過的黑洞AM.

testdb=# select a.amname, p.name, pg_indexam_has_property(a.oid,p.name)
testdb-# from pg_am a,
testdb-#      unnest(array['can_order','can_unique','can_multi_col','can_exclude']) p(name)
testdb-# order by a.amname;
    amname    |     name      | pg_indexam_has_property 
--------------+---------------+-------------------------
 blackhole_am | can_unique    | 
 blackhole_am | can_exclude   | 
 blackhole_am | can_multi_col | 
 blackhole_am | can_order     | 
 brin         | can_order     | f
 brin         | can_exclude   | f
 brin         | can_multi_col | t
 brin         | can_unique    | f
 btree        | can_order     | t
 btree        | can_unique    | t
 btree        | can_multi_col | t
 btree        | can_exclude   | t
 gin          | can_unique    | f
 gin          | can_order     | f
 gin          | can_multi_col | t
 gin          | can_exclude   | f
 gist         | can_unique    | f
 gist         | can_multi_col | t
 gist         | can_exclude   | t
 gist         | can_order     | f
 hash         | can_order     | f
 hash         | can_unique    | f
 hash         | can_multi_col | f
 hash         | can_exclude   | t
 heap         | can_multi_col | 
 heap         | can_unique    | 
 heap         | can_order     | 
 heap         | can_exclude   | 
 spgist       | can_multi_col | f
 spgist       | can_exclude   | t
 spgist       | can_unique    | f
 spgist       | can_order     | f
(32 rows)

PostgreSQL根據(jù)上述屬性判斷在創(chuàng)建索引時(shí)指定的option,如Hash索引不能是唯一索引(hash         | can_unique    | f):

testdb=# create unique index idx_t_idx1_id on t_idx1 using hash(id);
psql: ERROR:  access method "hash" does not support unique indexes

pg_index_has_property
test whether an index has a specified property

屬性名稱說明
clusterableCan the index be used in a CLUSTER command?
index_scanDoes the index support plain (non-bitmap) scans?
bitmap_scanDoes the index support bitmap scans?
backward_scanCan the scan direction be changed in mid-scan (to support FETCH BACKWARD on a cursor without needing materialization)?

創(chuàng)建hash索引,查詢?cè)撍饕南嚓P(guān)屬性

testdb=# create index idx_t_idx1_id on t_idx1 using hash(id);
CREATE INDEX
testdb=# select p.name, pg_index_has_property('idx_t_idx1_id'::regclass,p.name)
testdb-# from unnest(array[
testdb(#        'clusterable','index_scan','bitmap_scan','backward_scan'
testdb(#      ]) p(name);
     name      | pg_index_has_property 
---------------+-----------------------
 clusterable   | f
 index_scan    | t
 bitmap_scan   | t
 backward_scan | t
(4 rows)

pg_index_column_has_property
test whether an index column has a specified property

屬性名稱說明
ascDoes the column sort in ascending order on a forward scan?
descDoes the column sort in descending order on a forward scan?
nulls_firstDoes the column sort with nulls first on a forward scan?
nulls_lastDoes the column sort with nulls last on a forward scan?
orderableDoes the column possess any defined sort ordering?
distance_orderableCan the column be scanned in order by a “distance” operator, for example ORDER BY col <-> constant ?
returnableCan the column value be returned by an index-only scan?
search_arrayDoes the column natively support col = ANY(array) searches?
search_nullsDoes the column support IS NULL and IS NOT NULL searches?

查詢hash索引列的相關(guān)屬性(全為f - false)

testdb=# select p.name,
testdb-#      pg_index_column_has_property('idx_t_idx1_id'::regclass,1,p.name)
testdb-# from unnest(array[
testdb(#        'asc','desc','nulls_first','nulls_last','orderable','distance_orderable',
testdb(#        'returnable','search_array','search_nulls'
testdb(#      ]) p(name);
        name        | pg_index_column_has_property 
--------------------+------------------------------
 asc                | f
 desc               | f
 nulls_first        | f
 nulls_last         | f
 orderable          | f
 distance_orderable | f
 returnable         | f
 search_array       | f
 search_nulls       | f
(9 rows)

“怎么理解PostgreSQL的PG Index Properties”的內(nèi)容就介紹到這里了,感謝大家的閱讀。如果想了解更多行業(yè)相關(guān)的知識(shí)可以關(guān)注創(chuàng)新互聯(lián)-成都網(wǎng)站建設(shè)公司網(wǎng)站,小編將為大家輸出更多高質(zhì)量的實(shí)用文章!

名稱欄目:怎么理解PostgreSQL的PGIndexProperties-創(chuàng)新互聯(lián)
文章起源:http://bm7419.com/article22/dihgcc.html

成都網(wǎng)站建設(shè)公司_創(chuàng)新互聯(lián),為您提供網(wǎng)站設(shè)計(jì)、靜態(tài)網(wǎng)站品牌網(wǎng)站設(shè)計(jì)、虛擬主機(jī)、響應(yīng)式網(wǎng)站、移動(dòng)網(wǎng)站建設(shè)

廣告

聲明:本網(wǎng)站發(fā)布的內(nèi)容(圖片、視頻和文字)以用戶投稿、用戶轉(zhuǎn)載內(nèi)容為主,如果涉及侵權(quán)請(qǐng)盡快告知,我們將會(huì)在第一時(shí)間刪除。文章觀點(diǎn)不代表本網(wǎng)站立場(chǎng),如需處理請(qǐng)聯(lián)系客服。電話:028-86922220;郵箱:631063699@qq.com。內(nèi)容未經(jīng)允許不得轉(zhuǎn)載,或轉(zhuǎn)載時(shí)需注明來源: 創(chuàng)新互聯(lián)

綿陽服務(wù)器托管