timescale/tigerfs

Mount PostgreSQL as a filesystem. Build apps with files, explore databases with ls and cat. Every write is logged and undoable.

Owned by Timescale

View on GitHub ↗Jump to charts ↓

timescale/tigerfs has 700+ stars and 20+ forks on GitHub, is written in Go, and was last pushed on Oct 1, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 12th, 2026
Created on January 24th, 2026
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 25
Total Stargazers: 714 (+0)
Total Subscribers: 3 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.1 hours
Mean response time: 41.0 hours
90th percentile: 4.5 days
Tracked items: 5

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 113 days
Stale 30+ days: 3
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

TigerFS is a filesystem that mounts PostgreSQL databases as a virtual filesystem, allowing you to interact with database contents using standard file operations and command-line tools.

The tool solves the problem of database exploration and interaction by presenting PostgreSQL data through a familiar filesystem interface. Instead of writing SQL queries, users can browse database structure with ls, read data with cat, and perform writes through standard file operations. Every modification is logged and can be undone, providing an audit trail and safety mechanism for database changes. The approach works by implementing a FUSE-based filesystem layer that translates filesystem operations into corresponding PostgreSQL queries and transactions.

TigerFS suits developers and operators who want to explore databases interactively without learning or typing SQL, and teams building applications where file-based interfaces are more natural than direct database access. It is particularly useful for scenarios where you need to audit all changes to a database or want the ability to reverse modifications. The tool is appropriate for development and operational workflows where command-line familiarity is an advantage and where the overhead of filesystem abstraction is acceptable.

The project shows active development with regular commits across multiple areas of the codebase. Work spans core filesystem functionality, PostgreSQL integration, and tooling improvements, indicating sustained effort on both features and stability. The maintainers respond to issues and incorporate feedback, suggesting an engaged approach to user-reported problems. Documentation and examples receive attention alongside code changes, reflecting a commitment to usability.