@@ -793,15 +793,15 @@ The `order_by` attribute is one of the VOPS projection vector columns by which d
793
793
used in* time series* (for example trade date). Presence of such column in projection allows to incrementally update projection.
794
794
Generated` PNAME_refresh() ` method calls` populate ` method with correspondent values of` predicate ` and
795
795
` sort ` parameters, selecting from original table only rows with` order_by ` column value greater than maximal
796
- value of this column in projection. It assumes that` order_by ` is unique or at least refresh is done at the moment when there is some gap
796
+ value of this column inthe projection. It assumes that` order_by ` is unique or at least refresh is done at the moment when there is some gap
797
797
in collected events. In addition to` order_by ` , sort list for` populate ` includes all scalar (grouping) columns.
798
798
It allows to efficiently group imported data by scalar columns and fill VOPS tiles (vector columns) with data.
799
799
800
800
When` order_by ` attribute is specified, VOPS creates two functional BRIN indexes on` first() ` and` last() `
801
801
functions of this attribute. Presence of such indexes allows to efficiently select time slices. If original query contains
802
- predicates like` (trade_date between '01-01-2017' and '01-01-2018') ` then VOPS projection substitution mechanism adds
803
- ` (first(trade_date) >= '01-01-2017' and last(trade_date) >= '01-01-2018') ` conjuncts whichallows Postgres optimizer to use BRIN
804
- indexes to locate affected pages.
802
+ predicate like` (trade_date between '01-01-2017' and '01-01-2018') ` then VOPS projection substitution mechanism adds
803
+ ` (first(trade_date) >= '01-01-2017' and last(trade_date) >= '01-01-2018') ` conjuncts whichallow Postgres optimizer to use BRIN
804
+ index to locate affected pages.
805
805
806
806
In in addition to BRIN indexes for` order_by ` attribute, VOPS also creates BRIN index for grouping (scalar) columns.
807
807
Such index allows to efficiently select groups and perform index join.
@@ -821,7 +821,7 @@ Right now projections can be automatically substituted only if:
821
821
822
822
1 . Query doesn't contain joins.
823
823
2 . Query performs aggregation of vector (tile) columns.
824
- 3 . All other expressions in target list,` ORDER BY ` /` GROUP BY ` clausesrefers only to scalar attributes of projection.
824
+ 3 . All other expressions in target list,` ORDER BY ` /` GROUP BY ` clausesrefer only to scalar attributes of projection.
825
825
826
826
Projection can be removed using` drop_projection(projection_name text) ` function.
827
827
It not only drops the correspondent table, but also removes information about it from` vops_partitions ` table