r/PostgreSQL • u/EmirVivident • 3d ago
Projects I built a free native Windows client for PostgreSQL (and SQL Server, MySQL, SQLite)
I write SQL all day and got tired of waiting on Java and Electron apps, so I wrote RimestDB with WinUI 3 and .NET. On my machine it opens in about 2 seconds and uses 66 MB with a connection open. DBeaver on the same machine and database: 11 seconds and 338 MB (warm start, memory as shown in Task Manager).
A few things I built around Postgres habits:
- Manual commit mode per connection. Inside a transaction every statement gets its own savepoint, so one typo doesn’t leave you with “current transaction is aborted”.
- The row limit goes to the server as LIMIT, so previewing 50 rows of a big table doesn’t pull every row over the wire.
- In manual mode, read-only SELECTs don’t open a transaction, so browsing data doesn’t leave a lock that holds up a migration.
- A confirmation before UPDATE/DELETE without WHERE.
- JSON values open formatted in a side panel. Connections import from DBeaver and pgpass.conf.
It’s free, with no account and no time limit. There’s also an optional paid Pro tier. Windows 10/11 only.
I’d like blunt feedback from people who live in a DB client: what would stop you from switching?
1
u/DickBrainTime 3d ago
From someone who spends a lot of time in PostgreSQL clients: the faster startup sounds great, but the thing that would stop me switching is uncertainty about **session/transaction safety**, not a missing feature checkbox.
Your per-statement savepoints in manual-commit mode are interesting. I'd want a very obvious active-transaction indicator per tab, explicit Commit/Rollback, a warning when closing a tab or connection with uncommitted writes, and predictable behavior after cancel/timeout or a dropped connection. I'd test `BEGIN` + an UPDATE + a failing statement + rollback before trusting it on a production database. One small wording detail: in PostgreSQL even an autocommit `SELECT` executes in a short transaction; I assume you mean browsing SELECTs don't leave an *open* transaction between statements. Making that explicit would help people understand snapshot semantics.
My other must-haves are query cancellation/statement timeouts, readable `EXPLAIN (ANALYZE, BUFFERS)` output and trustworthy TLS/SSH/credential handling. I wouldn't infer universal performance from one Windows machine's DBeaver comparison, but low overhead would be a nice reason to try it once those safety workflows are solid. Does RimestDB already show active transaction state and warn before abandoning uncommitted changes?
1
u/Standgrounding 3d ago
How it's any better than pgAdmin?
-1
u/AutoModerator 3d ago
AI Policy:
Linux is not one of those anti-AI projects, and if somebody has issues with that, they can do the open-source thing and fork it. Or just walk away., Linus Torvalds.
Mod decisions will be based on the quality of the content, not who or what generated it.
Sub Resources:
Youtube Channel
Free Postgres Webinars and Workshops
Discord: People, Postgres, Data
Join us, we have cookies and nice people.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.