Project

General

Profile

Actions

Feature #4277

closed

Test split ranges in metadata table

Added by Pavel Kácha about 6 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Development - Core
Target version:
Start date:
08/21/2018
Due date:
% Done:

100%

Estimated time:
To be discussed:

Description

Queries involving ranges often fall down to the table scan or index scan. It may help to split out covering ranges from the events themselves into metadata table get them indexed, and extend the Source/Target queries by ANDing these covering ranges first. Queries then might end up using index for covering range (which would work for vast majority of events), and resort for doublechecking the array of IP ranges the hard way only on the result.

We count on pqsql planner cleverness here that it will use index to trim down the amount of hard scanned data when it makes sense by its data statistics.

It needs some tests.


Files

ip_aggr_test.py (1.42 KB) ip_aggr_test.py Radko Krkoš, 08/09/2019 10:03 AM

Related issues

Related to Mentat - Bug #4515: Runaway query?ClosedPavel Kácha01/14/2019

Actions
Actions

Also available in: Atom PDF