Indexes on Expressions

An index column need not be just a column of the underlying table, but can be a function or scalar expression computed from one or more columns of the table. This feature is

2016-10-12 11:33:25
Unique Indexes

Indexes can also be used to enforce uniqueness of a column's value, or the uniqueness of the combined values of more than one column.

2016-10-12 11:34:26
Multicolumn Indexes

An index can be defined on more than one column of a table. For example, if you have a table of this form:

2016-10-12 11:33:44
Examining Index Usage

Although indexes in PostgreSQL do not need maintenance or tuning, it is still important to check which indexes are actually used by the real-life

2016-10-12 11:33:17
Combining Multiple Indexes

A single index scan can only use query clauses that use the index's columns with operators of its operator class and are joined with AND. For example

2016-10-12 11:32:46
Index-Only Scans

All indexes in PostgreSQL are secondary indexes, meaning that each index is stored separately from the table's main

2016-10-12 11:33:25
Operator Classes and Operator Families

An index definition can specify an operator class for each column of an index.

2016-10-12 11:33:45
Index Types

PostgreSQL provides several index types: B-tree, Hash, GiST, SP-GiST, GIN and BRIN. Each index type uses a different algorithm that is best

2016-10-12 11:33:25
Indexes

Suppose we have a table similar to this: CREATE TABLE test1 ( id integer, content

2016-10-12 11:33:25
Partial Indexes

A partial index is an index built over a subset of a table; the subset is defined by a conditional expression (called the predicate

2016-10-12 11:33:46