catmaid / CATMAID
45%
master: 45%

LAST BUILD BRANCH: dev
DEFAULT BRANCH: master
Repo Added
Files 111
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH features/64-bit-concept-ids
branch: features/64-bit-concept-ids
CHANGE BRANCH
x

6757

push

travis-ci

tomka 
Make concept based table IDs 64 bit

While we still have some headroom for the datasets we work with at the
moment, keeping the IDs of concept table based tables (inheritance) at
32 bit would have been a limit at some point. Already we see large
segmentation datasets that make this headroom rather small. Therefore
this migration will rewrite all concept based tables as well as tables
that reference them through foreign keys so that 64 bit IDs are used.

This migration also updates the review table to use 64 bit IDs. It also
fixes the history views of the catmaid_sampler table, which haven't been
kept up to date with column changes.

In addition a lot of missing foreign key constraints have been added.
They shouldn't have a big import on performance and in fact only a very
small difference could be measured. Improved data security and
consistency is important and worth a small performance hit.

The column order of concept changed slightly to improve the column
alignment and reduce padding. So far we wasted 4 Bytes per row, because
project_id occupied 4 Bytes and required 4 Bytes of padding, because it
was followed by a bigint. This is changed now and no more padding is
needed. This also lowers the impact on storage of the change to 64 bit
IDs.

Also, the indices backing the primary keys of many semantic tables
include now additional data like the class_id for class instances and
the relation_id for some relation instance types. This Postgres 11
feature allows to use more index-only scans. This is especially useful
when traversing join tables likes class_instance_class_instancem, since
connections between them can now be found with index-only scans alone.

In addition many index names follow now a more consistent pattern.

I tested this migration by multiple reviews and analyzing the schema
diff generated by pgquarrel for both migration 98 vs 99 as well as 99 vs
(99 -> 98) (i.e. a rollback). These migrations look reasonable and the
effective migration (... (continued)

8705 of 19283 relevant lines covered (45.14%)

1.68 hits per line

Relevant lines Covered
19283 RELEVANT LINES 8705 COVERED LINES
1.68 HITS PER LINE
Source Files on features/64-bit-concept-ids
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
6757 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... push tomka travis-ci pending completion  
6756 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... Pull #1887 web-flow travis-ci pending completion  
6753 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... Pull #1887 web-flow travis-ci pending completion  
6752 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... push tomka travis-ci pending completion  
6751 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... Pull #1887 web-flow travis-ci pending completion  
6750 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... push tomka travis-ci pending completion  
6747 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... Pull #1887 web-flow travis-ci pending completion  
6746 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... push tomka travis-ci pending completion  
6745 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... Pull #1887 web-flow travis-ci pending completion  
6744 features/64-bit-concept-ids Make concept based table IDs 64 bit While we still have some headroom for the datasets we work with at the moment, keeping the IDs of concept table based tables (inheritance) at 32 bit would have been a limit at some point. Already we see large s... push tomka travis-ci pending completion  
See All Builds (4802)