Contents

CREATE INDEX idx_events_global_position_including_type ON public.events USING btree (global_position) INCLUDE (type);
COMMENT ON INDEX idx_events_global_position_including_type IS 'Usually "type" column has low distinct values. Thus, composit index by "type" and "global_position" columns may not be picked by Query Planner properly. Improve an index by "global_position" by including "type" column which allows Query Planner to perform better by picking the correct index.';

DROP INDEX idx_events_global_position;

Version data entries

10 entries across 10 versions & 1 rubygems

Version	Path
pg_eventstore-0.6.0	db/migrations/2_adjust_global_position_index.sql
pg_eventstore-0.5.3	db/migrations/2_adjust_global_position_index.sql
pg_eventstore-0.5.2	db/migrations/2_adjust_global_position_index.sql
pg_eventstore-0.5.0	db/migrations/2_adjust_global_position_index.sql
pg_eventstore-0.4.0	db/migrations/2_adjust_global_position_index.sql
pg_eventstore-0.3.0	db/migrations/2_adjust_global_position_index.sql
pg_eventstore-0.2.6	db/migrations/2_adjust_global_position_index.sql
pg_eventstore-0.2.5	db/migrations/2_adjust_global_position_index.sql
pg_eventstore-0.2.4	db/migrations/2_adjust_global_position_index.sql
pg_eventstore-0.2.3	db/migrations/2_adjust_global_position_index.sql