Skip to main content

tigrbl_engine_postgres

Tigrbl logo

PostgreSQL engine plugin for SQLAlchemy sessions, async database workflows, and Tigrbl application persistence.

PyPI version for tigrbl_engine_postgres Downloads for tigrbl_engine_postgres Discord community for tigrbl_engine_postgres Repository hits for tigrbl_engine_postgres README Apache 2.0 license Python versions 3.10 | 3.11 | 3.12 | 3.13 | 3.14 for tigrbl_engine_postgres Workspace group for tigrbl_engine_postgres

What is tigrbl_engine_postgres?

PostgreSQL engine plugin for SQLAlchemy sessions, async database workflows, and Tigrbl application persistence.

Why use tigrbl_engine_postgres?

Use it when a Tigrbl application needs this backend without installing every engine package.

When should I install tigrbl_engine_postgres?

Install it when the storage, analytics, cache, or integration workload named by this package is the intended runtime backend.

Who is tigrbl_engine_postgres for?

Application developers, data platform engineers, and operators choosing concrete persistence or data-plane behavior.

Where does tigrbl_engine_postgres fit?

tigrbl_engine_postgres lives at pkgs/90_engines/tigrbl_engine_postgres and serves PostgreSQL-backed production persistence and SQLAlchemy workflows.

How does tigrbl_engine_postgres work?

It exposes a tigrbl.engine entry point and a package register() hook so Tigrbl can discover or load the backend at runtime.

Install

uv add tigrbl_engine_postgres
pip install tigrbl_engine_postgres

Surface Coverage

Surface Value
PyPI package tigrbl_engine_postgres
Repository path pkgs/90_engines/tigrbl_engine_postgres
Python import root tigrbl_engine_postgres
Console scripts none declared
Entry points tigrbl.engine
Optional extras none declared
Legal files LICENSE, NOTICE
Supported Python `3.10

What It Owns

tigrbl_engine_postgres owns the engine plugin boundary. It should be installed when you need this package's focused responsibility without assuming every other Tigrbl workspace package is present.

Implementation orientation:

  • tigrbl_engine_postgres: engine, plugin, session

Public API and Import Surface

  • Import roots: tigrbl_engine_postgres.
  • Public symbols: PostgresSession, postgres_capabilities, postgres_engine, register.
  • Workspace dependencies: tigrbl.
  • External runtime dependencies: SQLAlchemy>=2.0,<3.0, psycopg[binary]>=3.1,<4.0.

Usage Examples

Verify the installed package

python -m pip show tigrbl_engine_postgres
python - <<'PY'
from importlib.metadata import version
print(version("tigrbl_engine_postgres"))
PY

Register the engine plugin explicitly

from tigrbl_engine_postgres import register

register()

Discover the engine through package metadata

from importlib.metadata import entry_points

for entry_point in entry_points(group="tigrbl.engine"):
    if entry_point.module.startswith("tigrbl_engine_postgres"):
        plugin_register = entry_point.load()
        plugin_register()

Install alongside the facade

uv add tigrbl tigrbl_engine_postgres
pip install tigrbl tigrbl_engine_postgres

How To Choose This Package

Choose tigrbl_engine_postgres when the quick-answer table matches your use case. Choose tigrbl instead when you want the full public facade. Choose a lower-level package such as tigrbl-core, tigrbl-base, or tigrbl-runtime when you are building framework extensions or testing a specific internal boundary.

Support

Package-local Boundary

This README is the package-local distribution entry point for tigrbl_engine_postgres. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.

Certification Status

  • Package status: governed package in the tigrbl/tigrbl workspace.
  • Governance source: SSOT registry.
  • Release evidence: publish workflow validates package builds, tests, GitHub release assets, and PyPI publication for managed packages.
  • Local certification guard: pkgs/97_tests/tigrbl_tests/tests/unit/test_package_badges_and_notices.py verifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge, LICENSE, and NOTICE.
  • Scope note: this README documents the package boundary. Runtime feature support remains governed by .ssot/ entities and the conformance docs linked below.

License

Licensed under the Apache License, Version 2.0. See LICENSE, NOTICE, and the official Apache 2.0 license text.

Metadata

Release files for tigrbl_engine_postgres 0.4.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tigrbl_engine_postgres 0.4.5
File Size Uploaded Provenance Actions
tigrbl_engine_postgres-0.4.5.tar.gz 11.7 kB Without provenance Details for tigrbl_engine_postgres-0.4.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tigrbl_engine_postgres 0.4.5
File Interpreter ABI Platform Actions
tigrbl_engine_postgres-0.4.5-py3-none-any.whl Python 3 none any Details for tigrbl_engine_postgres-0.4.5-py3-none-any.whl

Total release size: 26.8 kB

Release files / tigrbl_engine_postgres-0.4.5.tar.gz

Download URL tigrbl_engine_postgres-0.4.5.tar.gz
Size 11.7 kB
Tags Source
SHA-256 checksum
How to use checksums
33e5b5c44e4a56336fa5e3ee25cef2a802f5d4c7f72195a7ac8a99422cf1e83c
BLAKE2b-256 checksum
How to use checksums
ac09f30c81d88f91c80990da3c3263e1f37c9fe057866fe8fa29d276d846ec59
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / tigrbl_engine_postgres-0.4.5-py3-none-any.whl

Download URL tigrbl_engine_postgres-0.4.5-py3-none-any.whl
Size 15.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
332bc859aa848b2bb90139d9fe2b2eff653dd08ffec9d4c601fa47914afeb775
BLAKE2b-256 checksum
How to use checksums
814fa9b2a3d583ff55b4a2f315b4a3906db126c1d238be7e54581d54d0908fc8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for tigrbl_engine_postgres 0.4.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page