Projection Row Counts Different

[Josh]

Hi guys,

Can someone help explain why different projections for the same table on the same node can have different row counts. Here is an example on my database. See that the projections storeb_b0 and storeb_b1 have different row counts but I don't know why.

Code: Select all

dbadmin=> select node_name, projection_name, ros_row_count, wos_row_count, row_count
dbadmin-> from PROJECTION_STORAGE
dbadmin-> where anchor_table_schema = 'vertica01'
dbadmin->   and anchor_table_name = 'storeb'
dbadmin-> order by 1, 2, 3;
      node_name       | projection_name | ros_row_count | wos_row_count | row_count
----------------------+-----------------+---------------+---------------+-----------
 v_vertica01_node0001 | storeb_b0       |       1438899 |             0 |   1438899
 v_vertica01_node0001 | storeb_b1       |       1374028 |             0 |   1374028
 v_vertica01_node0002 | storeb_b0       |       1374189 |             0 |   1374189
 v_vertica01_node0002 | storeb_b1       |       1438899 |             0 |   1438899
 v_vertica01_node0003 | storeb_b0       |       1374028 |             0 |   1374028
 v_vertica01_node0003 | storeb_b1       |       1374189 |             0 |   1374189
(6 rows)

Thanks.

[id10t]

Hi!

Segmentation

[scutter]

To elaborate on the previous response - the row counts are the same, just offset by one node. This is how high availabilty is achieved - having the same data available on multiple nodes. The row count for the data on node0001 for storeb_b0 is the same as the row count on node0002 for storeb_b1.