Looking Inside Postgres at a GiST Index
Looking Inside Postgres at a GiST Index
What does the GiST API do? And what does it mean to extend Postgres’s indexing system, exactly? Read on to find out!
Join the DZone community and get the full member experience.Join For Free
Built by the engineers behind Netezza and the technology behind Amazon Redshift, AnzoGraph™ is a native, Massively Parallel Processing (MPP) distributed Graph OLAP (GOLAP) database that executes queries more than 100x faster than other vendors.
In the last few posts in this series (one, two, three, and four), I showed you how to save hierarchical data into a flat database table using the Postgres LTREE extension. I explained that you represent tree nodes using path strings and how to search your tree data using special SQL operators LTREE provides.
But the real value of LTREE isn’t the operators and functions it gives you — internally, these boil down to fairly simple string operations. Instead, what makes LTREE useful is that it integrates these new operators with Postgres’s indexing code, which allows you to search for and find matching tree paths quickly. To achieve this, LTREE takes advantage of the Generalized Search Tree (GiST) project, an API that allows C developers to extend Postgres’s indexing system.
But what does the GiST API do? And what does it mean to extend Postgres’s indexing system, exactly? Read on to find out!
Searching Without an Index
Here again is the tree table I used as an example in the earlier posts in this series:
create table tree( id serial primary key, letter char, path ltree );
Note that the
path column uses the custom
ltree data type that the LTREE extension provides. If you missed the previous posts,
ltree columns represent hierarchical data by joining strings together with periods, i.e.
Earlier, I used a simple tree with only seven nodes as an example. SQL operations on a small table like this will always be fast. Today, I’d like to imagine a much larger tree to explore the benefits indexes can provide. Suppose that instead I have a tree containing hundreds or thousands of records in the path column:
Now, suppose I search for a single tree node using a
select letter from tree where path = 'A.B.T.V'
Without an index on this table, Postgres has to resort to a sequence scan, which is a technical way of saying that Postgres has to iterate over all of the records in the table:
For each and every record in the table, Postgres executes a comparison
p == q where
p is the value of the path column for each record in the table, and q is the query, or the value I’m searching for (
A.B.V.T in this example). This loop can be very slow if there are many records. Postgres has to check all of them because they can appear in any order and there’s no way to know how many matches there might be in the data ahead of time.
Searching With a B-Tree Index
Of course, there’s a simple solution to this problem. I just need to create an index on the path column:
create index tree_path_idx on tree (path);
As you probably know, executing a search using an index is much faster. If you see a performance problem with a SQL statement in your application, the first thing you should check for is a missing index. But why? Why does creating an index speed up searches, exactly? The reason is that an index is a sorted copy of the target column’s data:
By sorting the values ahead of time, Postgres can search through them much more quickly. It uses a binary search algorithm:
Postgres starts by checking the value in the middle of the index. If the stored value (
p) is too large and is greater than the query (
p > q, it moves up and checks the value at the 25% position. If the value is too small, if
p < q, it moves down and checks the value at the 75% position. Repeatedly dividing the index into smaller and smaller pieces, Postgres only needs to search a few times before it finds the matching record or records.
However, for large tables with thousands or millions of rows, Postgres can’t save all of the sorted data values in a single memory segment. Instead, Postgres indexes (and indexes inside of any relational database system) save values in a binary or balanced tree (B-Tree):
Now, my values are saved in a series of different memory segments arranged in a tree structure. Dividing the index up into pieces allows Postgres to manage memory properly while saving possibly millions of values in the index. Note that this isn’t the tree from my LTREE dataset; B-Trees are internal Postgres data structures I don’t have access to. To learn more about the computer science behind this, read my 2014 article Discovering the Computer Science Behind Postgres Indexes.
Now, Postgres uses repeated binary searches — one for each memory segment in the B-Tree — to find a value:
Each value in the parent or root segment is really a pointer to a child segment. Postgres first searches the root segment using a binary search to find the right pointer and then jumps down to the child segment to find the actual matching records using another binary search. The algorithm is recursive; the B-Tree could contain many levels in which case the child segments would contain pointers to grandchild segments, etc.
What’s the Problem With Standard Postgres Indexes?
But there’s a serious problem here I’ve overlooked so far. Postgres’s index search code only supports certain operators. Above, I was searching using this select statement:
select letter from tree where path = 'A.B.T.V'
I was looking for records that were equal to my query:
p == q. Using a B-Tree index, I could also have searched for records greater than or less than my query:
p < q or
p > q.
But what if I want to use the custom
LTREE <@ (ancestor) operator? What if I want to execute this
select letter from tree where path <@ 'A.B.V'
As we saw in the previous posts in this series, this search will return all of the LTREE records that appear somewhere on the branch under A.B.V, that are descendants of the A.B.V tree node.
A standard Postgres index doesn’t work here. To execute this search efficiently using an index, Postgres needs to execute this comparison as it walks the B-Tree:
p <@ q. But the standard Postgres index search code doesn’t support
p <@ q. Instead, if I execute this search Postgres resorts to a slow sequence scan again, even if I create an index on the ltree column.
To search tree data efficiently, we need a Postgres index that will perform
p <@ q comparisons equally well as
p == q and
p < q comparisons. We need a GiST index!
The Generalized Search Tree (GiST) Project
Almost 20 years ago, an open-source project at UC Berkeley solved this precise problem. The Generalized Search Tree (GiST) project added an API to Postgres allowing C developers to extend the set of data types that can be used in a Postgres index.
Quoting from the project’s web page:
In the beginning, there was the B-tree. All database search trees since the B-tree have been variations on its theme. Recognizing this, we have developed a new kind of index called a Generalized Search Tree (GiST), which provides the functionality of all these trees in a single package. The GiST is an extensible data structure, which allows users to develop indices over any kind of data, supporting any lookup over that data.
GiST achieves this by adding an API to Postgres’s index system anyone can implement for their specific data type. GiST implements the general indexing and searching code but calls out to custom code at four key moments in the indexing process. Quoting from the project’s web page again, here’s a quick explanation of the four methods in the GiST API:
GiST indexes use a tree structure similar to the B-Tree we saw above. But Postgres doesn’t create the GiST index tree structure by itself; Postgres works with implementations of the GiST Union, Penalty and PickSplit API functions described above. And when you execute a SQL statement that searches for a value in a GiST index, Postgres uses the Consistent function to find the target values.
The key here is the implementor of the GiST API can decide what type of data to index and how to arrange those data values in the GiST tree. Postgres doesn’t care what the data values are or how the tree looks. Postgres simply calls Consistent any time it needs to search for a value and lets the GiST API implementor find the value.
An example would help understand this, and we have an example GiST API implementation: The LTREE extension!
Implementing the GiST API for Tree Paths
Starting in around 2001, two students at Moscow State University found the API from the GiST project and decided to use it to build indexing support for tree data. Oleg Bartunov and Teodor Sigaev, in effect, wrote a “Tree Paths Consistent” function, a “Tree Path Union” function, etc. The C code that implements this API is the LTREE extension. You can find these functions,
ltree_union, among other functions, in a file called
ltree_gist.c, located in the
contrib/ltree directory in the Postgres source code. They also implemented the Penalty, PickSplit and various other functions related to the GiST algorithm.
I can use these custom functions on my own data simply by creating a GiST index. Returning to my LTREE example, I’ll drop my B-Tree index and create a GiST index instead:
drop index tree_path_idx; create index tree_path_idx on tree using gist (path);
Notice the using gist keywords in the create index command. That’s all it takes; Postgres automatically finds, loads, and uses the
ltree_picksplit, etc., functions whenever I insert a new value into the table. (It will also insert all existing records into the index immediately.) Of course, earlier, I installed the LTREE extension also.
Let’s see how this works. Suppose I add a few random tree records to my empty tree table after creating the index:
insert into tree (letter, path) values ('A', 'A.B.G.A'); insert into tree (letter, path) values ('E', 'A.B.T.E'); insert into tree (letter, path) values ('M', 'A.B.R.M'); insert into tree (letter, path) values ('F', 'A.B.E.F'); insert into tree (letter, path) values ('P', 'A.B.R.P');
To get things started, Postgres will allocate a new memory segment for the GiST index and insert my five records:
If I search now using the ancestor operator:
select count(*) from tree where path <@ 'A.B.T'
…Postgres will simply iterate over the records in the same order I inserted then and call the
ltree_consistent function for each one. Here again is what the GiST API calls for the Consistent function to do:
In this case, Postgres will compare
p <@ A.B.T for each of these five records:
Because the values of
p, the tree page keys, are simple path strings,
ltree_consistent directly compares them with
A.B.T and determines immediately whether each value is a descendant tree node of
A.B.T. Right now, the GiST index hasn’t provided much value; Postgres has to iterate over all the values, just like a sequence scan.
Now, suppose I start to add more and more records to my table. Postgres can fit up to 136 LTREE records into the root GiST memory segment, and index scans function the same way as a sequence scan by checking all the values.
But if I insert one more record, the 137th record doesn’t fit. At this point, Postgres has to do something different:
Now, Postgres “splits” the memory segment to make room for more values. It creates two new child memory segments and pointers to them from the parent or root segment.
What does Postgres do next? What does it place into each child segment? Postgres leaves this decision to the GiST API, to the LTREE extension, by calling the the
ltree_picksplit function. Here again is the API spec for PickSplit:
ltree_picksplit function — the LTREE implementation of the GiST API — sorts the tree paths alphabetically and copies each half into one of the two new child segments. Note that GiST indexes don’t normally sort their contents; however, GiST indexes created specifically by the LTREE extension do because of the way
ltree_picksplit works. We’ll see why it sorts the data in a moment.
Now, Postgres has to decide what to leave in the root segment. To do this, it calls the Union GiST API:
In this example, each of the child segments is a set
S. And the
ltree_union function has to return a “union” value for each child segment that describes somehow what values are present in that segment:
Oleg and Teodor decided this union value should be a pair of left/right values indicating the minimum and maximum tree branches inside of which all of the values fit alphabetically. This is why the ltree_picksplit function sorted the values. For example, because the first child segment contains the sorted values from A.B.C.B through A.B.M.Z, the left/right union becomes A and A.B.M:
A.B.M is sufficient here to form a union value excluding
A.B.N.X and all the following values; LTREE doesn’t need to save
Similarly, the left/right union for the second child segment becomes
This is what a GiST index looks like — or, what an LTREE GiST index looks like, specifically. The power of the GiST API is that anyone can use it to create a Postgres index for any type of data. Postgres will always use the same pattern: The parent index page contains a set of union values, each of which somehow describes the contents of each child index page.
For LTREE GiST indexes, Postgres saves left/right value pairs to describe the union of values that appear in each child index segment. For other types of GiST indexes, the union values could be anything. For example, a GiST index could store geographical information like latitude/longitude coordinates, or colors, or any sort of data at all. What’s important is that each union value describe the set of possible values that can appear under a certain branch of the index. And like B-Trees, this union value/child page pattern is recursive: A GiST index could hold millions of values in a tree with many pages saved in a large multi-level tree.
Searching a GiST Index
After creating this GiST index tree, searching for a value is straightforward. Postgres uses the ltree_consistent function. As an example, let’s repeat the same SQL query from above:
select count(*) from tree where path <@ 'A.B.T'
To execute this using the GiST index, Postgres iterates over the union values in the root memory segment and calls the
ltree_consistent function for each one:
Now, Postgres passes each union value to
ltree_consistent to calculate the
p <@ q formula. The code inside of
ltree_consistent then returns
q > left and
q < right. Otherwise, it returns
In this example, you can see
ltree_consistent finds that the query
MAYBE is located inside the second child memory segment, but not the first one.
For the first child union structure,
q > A true but
q < A.B.M false. Therefore,
ltree_consistent knows there can be no matches in the top child segment, so it skips down to the second union structure.
For the second child union structure,
ltree_consistent finds both
q > A.B.N true and
q < A.B.X true. Therefore, it returns
MAYBE, meaning the search continues in the lower child segment:
Note that Postgres never had to search the first child segment: The tree structure limits the comparisons necessary to only the values that might match
p <@ A.B.T.
Imagine my table contained a million rows. Searches using the GiST index will still be fast because the GiST tree limits the scope of the search. Instead of executing
p <@ q on every one of the million rows, Postgres only needs to run
p <@ q a handful of times, on a few union records and on the child segments of the tree that contain values that might match.
Send Them a Postcard
Oleg Bartunov and Teodor Sigaev, the authors of the LTREE extension, explain its usage and the algorithms I detailed above here on their web page. They included more examples of SQL searches on tree data, including some which use the
LTREE data type I didn’t have time to cover in these blog posts.
But most importantly, they included this note at the bottom:
Do you save tree data in Postgres? Does your app take advantage of the LTREE extension? If so, you should send Oleg and Teodor a postcard! I just did.
Published at DZone with permission of Pat Shaughnessy , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.