Last week, dbForge released version 2026.2, and one thing that stood out to me was the new embedded debugger for PostgreSQL in dbForge Studio. It's a brand-new addition that PostgreSQL developers will definitely appreciate.

Here's what it lets you do:

• Set breakpoints at specific lines to pause execution exactly where you need to
• Step through your code line by line to see the order operations actually run in
• Monitor the current values of variables, expressions, and query results as the code executes
• Handle exceptions with the exact line where the error occurs highlighted, instead of tracing it back manually

Because it's embedded, there's no extension to install and no separate configuration step. You update dbForge Studio for PostgreSQL, and the debugging tools are already there.

For anyone working with functions that have multiple branches, procedures that touch several tables, or triggers with conditional logic, this makes it much easier to see exactly what's happening at each step rather than infer it from the final result. It's a straightforward addition, but one that changes how you approach debugging PostgreSQL code every day.

The debugger is the main event in this release, but it shipped alongside a few other updates worth knowing about:

• Broader context awareness in dbForge AI Assistant, including file attachments, multi-database support, plus a new free Express edition of dbForge AI Assistant
• New visual editors for PostgreSQL functions, procedures, and event triggers
• Object and column name qualification for already written code and wildcard expansion in dbForge SQL Complete and dbForge Studios for SQL Server, MySQL, and Oracle
• Quicker data generation straight from Database Explorer
• A simplified sign-in option for product activation

Together, they make this a release worth updating, even if the PostgreSQL debugger alone wasn't enough to convince you.