Postgres extension for an integer hierarchical data type like: 1.2.3.500, for up to 16 segments with positive int values >= 1 and <= 65535, inspired by the great extension LTREE.
The main use case for itree is keys of ontologies or any hierarchical reference data.
TODO: add an example of Type for Single Table Inheritance pattern.
Some basic operators are provided initially, more are added as needed.
| Operator | Description |
|---|---|
| itree @> itree → boolean | Is left argument an ancestor of right (or equal as ltree) |
| itree <@ itree → boolean | Is left argument a descendant of right (or equal as ltree) |
| itree || itree -> itree | concatenate 2 itree values |
| itree || int -> itree | concatenate itree and an int |
| itree || text -> itree | concatenate itree and a text tree |
| Function | Description | Example |
|---|---|---|
| ilevel(itree) -> integer | number of levels | ilevel('1.2.3') -> 3 |
| subpath ( itree, offset integer, len integer ) → itree | Returns subpath of itree starting at position offset, with length len. | subpath('1.2.3.4.5', 0, 2) → 1.2 |
| subitree ( itree, start integer, end integer ) → itree | Returns subpath of itree from position start to position end-1 (counting from 0). | subitree('1.2.3.4', 1, 2) → 2 |
itree uses a fixed length 18 bytes with 2 control and 16 data bytes, which hold segments with variable length from 1 to 2 bytes per segment.
Control bits 0-15 with a value of 1 indicate a new segment in the relevant data byte, while 0 means the data byte is added to the previous segment.
Segment value 0 is disallowed as it is interpreted as an end of the itree when its control bit is 1.
- B-tree over itree: <, <=, =, >=, >
- GIN index over(itree_gin_ops opclass): <, <=, =, >=, > <@, @>
- TODO: GiST and compare performance with GIN using high and low cardinality
Example of creating a GIN index:
CREATE TABLE reference_data (id itree, label text, label_path ltree);
CREATE TABLE entity(id uuid, reference_id itree references reference_data(id));
CREATE INDEX itree_gin_idx ON entity USING GIN (reference_id itree_gin_ops);Test python/sqlalchemy support:
1.uv sync
2. source .venv/bin/activate
2. pytest -s test.py
You can use itree with SQLModel/SQLAlchemy similar to Ltree fround in sqlaclhemy-utils:
from sqlmodel import Column, Field, SQLModel
from sqlalchemy_utils import Ltree, LtreeType
from app.util.itree import ITree, ITreeType
class Entity(SQLModel, table=True):
"""A test class to check database connectivity and extensions support."""
model_config = ConfigDict(arbitrary_types_allowed=True)
id: uuid.UUID = Field(default_factory=uuid7, primary_key=True)
path: Ltree = Field(sa_column=Column(LtreeType, nullable=False))
ipath: ITree = Field(sa_column=Column(ITreeType, nullable=False))
...
e = Entity(
path= Ltree('Test.Ltree.Support'),
ipath= ITree('1.2.3'),
)
db.add(e)
db.commit()- Edit the sample Dockerfile and build it with docker:
docker build -t postgres-itree .
and run with:docker run -d --name postgres-itree-standalone -e POSTGRES_PASSWORD=secret -p 5432:5432 postgres-itree - or modify
.envand use the sampledocker-compose.yml:docker-compose up -d
For hacking itree you need to build Postgres from source:
-
Download Postgres source
git clone https://github.com/postgres/postgres.git -
Install Prerequisites
sudo apt-get install build-essential libreadline-dev zlib1g-dev flex bison pkg-config libicu-dev -
Configure
cd postgres
./configure --enable-debug --enable-cassert- Build
make
sudo make install-
Init Postgres
For dev purpose the current user will own and run the postgres server.
sudo chown -R $USER$ /usr/local/pgsql
initdb -D /usr/local/pgsql/data -
Start the server with log to the console
pg_ctl -D /usr/local/pgsql/data startYou can addPGDATA=/usr/local/pgsql/datato your env and use onlypg_ctl start -
Login as the current user.
psql -d postgresYou create a new database with the name of the current user and log with onlypsql.
-
Checkout itree code
cd postgres/contrib/
git clone https://github.com/chernia/itree.git -
Compile and install.
make clean
make CFLAGS="-std=c99 -g -O0"
make install-
restart postgres
pg_ctl -D /usr/local/pgsql/data restart -
Run tests
make installcheck
- .vscode/launch.json linux
{
"version": "0.2.0",
"configurations": [
{
"name": "Attach to PostgreSQL Backend",
"type": "cppdbg",
"request": "attach",
"program": "/usr/local/pgsql/bin/postgres",
"processId": "${command:pickProcess}",
"MIMode": "gdb",
"setupCommands": [
{"text": "-enable-pretty-printing", "ignoreFailures": true},
{"text": "sharedlibrary itree"},
{"text": "break itree_in"},
{"text": "handle SIGSEGV stop print"}
]
}
]
}- .vscode/launch.json macos
{
"version": "0.2.0",
"configurations": [
{
"name": "Attach to PostgreSQL Backend",
"type": "cppdbg",
"request": "attach",
"program": "/usr/local/pgsql/bin/postgres",
"processId": "${command:pickProcess}",
"MIMode": "lldb",
"setupCommands": [
{
"description": "Enable pretty-printing for lldb",
"text": "settings set target.inline-breakpoint-strategy always",
"ignoreFailures": true
},
{
"description": "Break on itree_in function",
"text": "breakpoint set --name itree_in",
"ignoreFailures": true
}
],
"osx": {
"MIMode": "lldb"
}
}
]
}- Get the backend process id of the
psqlsession
CREATE EXTENSION itree;
SELECT pg_backend_pid();
- Load itree in the psql session
select '1.2.3'::itree; - Get <backend_pid> with:
select pg_backend_pid(); - Attach GDB
- Add a breakpoint
gdb /usr/local/pgsql/bin/postgres <backend_pid>
(gdb) sharedlibrary itree
(gdb) break itree_in
(gdb) handle SIGSEGV stop print
(gdb) continuemake installcheck will run the sdl/itree.sql and compare with expected/itree.out
Itree is released under the MIT License.
Copyright 2025 Ivan Stoev
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.