Following VS Code guidance, the PostgreSQL extension uses odd minor version numbers for pre-releases and even minor version numbers for stable releases.
Read more about pre-release versioning behavior for extensions in the VS Code documentation.
- Restored interactive Microsoft Entra sign-in for affected users who encountered a blank browser page and error 70007 when adding or reauthenticating an account. (#303)
Stable release.
This is the stable release of the features introduced in 1.29.*. There are no changes since 1.29.1, but 1.30.0 marks these features as stable for all users.
- Elastic Cluster support — Elastic clusters in Azure Database for PostgreSQL flexible server now have a dedicated management dashboard for connection endpoints and worker-node topology, Azure Monitor CPU and disk metrics, table distribution, shard placement and skew analysis, colocation groups, and reviewable SQL for table and shard operations. Object Explorer also identifies clusters with distinct connected and disconnected icons and highlights distribution-key columns, while Server Logs points to supported diagnostic alternatives when downloads are unavailable.
- Azure HorizonDB metrics — Explore Azure Monitor-backed health and performance metrics, active sessions and wait activity, server details, and Query Store readiness guidance from the Server Dashboard.
- Customizable Performance Dashboard views — Choose which charts, metric cards, tables, and trees appear on each dashboard tab, with selections saved independently for each connection.
- [Schema Migrations] Review conversion work with a consistent Converted or Not-Converted status and
CVT-NNNmessages that explain the outcome and recommended action. The Grouped and Tasks tabs show the same Action Item population, keep package members together, and show full error details. - [Schema Migrations] Surface customer obligations as Action Items, including autonomous transactions, database links, required extensions, and non-functional bodies.
- [Schema Migrations] Add a customer object-mapping summary and cleaner conversion reports.
- [Schema Migrations] Diagnose compile-barrier failures so dependency and compile findings are visible and actionable.
- [Schema Migrations] Automatically recover failed conversion chunks when a later pass can salvage already-converted records.
- Query Plan Visualizer Buffer Hits now show exclusive/self values when Self is selected, and cumulative values for Total. (#292)
- Azure Browse uses the server's real fully qualified domain name instead of synthesizing
*.postgres.database.azure.com, so regional and custom Flexible Server endpoints can connect. - Azure Dashboard metadata discovery now validates Flexible Servers by ARM resource identity, so custom/regional hostnames still get Azure management features.
- Unresolved Azure browse endpoints are no longer turned into guessed hostnames.
- Concurrent Azure management operations now share an in-flight token request, preventing overlapping refreshes from leaving dashboard or Server Logs features stuck loading.
- Oracle schema discovery in a migration project now reports the connection error instead of spinning on Loading... forever.
- [Schema Migrations] Conversion completion and conversion success are now distinct, while reports consistently identify incomplete or missing artifacts, never-attempted objects, widened conversion scope, empty fallback output, and package-member outcomes.
- [Schema Migrations] Reject converted DDL that would execute nothing, and stop shipping broken identifiers or unparseable PL/pgSQL bodies.
- [Schema Migrations] Preserve Oracle database-link atomicity instead of silently dropping those guarantees.
- [Schema Migrations] A transient failure converting one package member no longer aborts the whole package.
- [Schema Migrations] Deploy preparation now enforces roster coverage and can salvage converted records from failed chunks.
- [Schema Migrations]
pg_cronis no longer treated as a generally required target-database extension or used to block jobs conversion. - [Schema Migrations] Conversion no longer fails solely because
plpgsql_checkis unavailable; reports identify when dependency validation was relaxed. - [Schema Migrations] Conversion is more reliable across Windows client configuration, resumed runs, dropped connections, deadlines, failed savepoint rollbacks, large decomposed packages, and Oracle
GOTOtransformations. - [Schema Migrations] Primary-key conversion now handles
ALTER TABLE IF EXISTSwithout generating redundant primary-key work.
Stable release.
This is the stable release of the features introduced in 1.27.*.
- Database Backup (Preview) — Choose Backup... from a server or database in Object Explorer to create a
pg_dumpbackup. Configure the output format, schema/data scope, object filters, compression, parallel jobs, and advanced options, then monitor or cancel the backup from VS Code. (#257) - Database Restore (Preview) — Choose Restore... from a server or database in Object Explorer to restore from a backup file. Pick a target database and restore mode (full, schema-only, or data-only), preview the generated command, and watch live progress with the option to cancel. (#257)
- Get Started page — After saving a new connection, a Get Started tab points you at your likely next step: open a new query, view the performance dashboard, browse features, or start an AI chat scoped to the selected database. Reopen it any time from Object Explorer, or turn the automatic prompt off from the page itself.
- Azure Database for PostgreSQL Elastic Clusters — Provision Elastic Cluster (Citus) deployments with a configurable node count. Object Explorer now identifies distributed, reference, local, and distributed-schema tables with distinct icons and labels.
- [Schema Migrations] - Convert Oracle object types (
TYPEandTYPE BODY) to PostgreSQL. - [Schema Migrations] - Use plpgsql_check extension for better conversion of programmable objects.
- [Schema Migrations] - Use Azure HorizonDB as target.
- Azure metadata requests now work correctly in the packaged extension, so Azure sign-in and resource browsing behave the same as in development builds.
- Edit Data now defaults to stable key-column ordering when no explicit sort is selected.
- Expired Microsoft Entra tokens no longer start duplicate reconnects or cause stuck connection progress, broad pool-timeout warnings, and Object Explorer disconnects during metadata refresh.
- [Schema Migrations] - Support conversion for wrapped Oracle objects, hierarchical queries.
- [Schema Migrations] - Package performance optimization, handle large packages.
- [Schema Migrations] - Fixes for better conversion of dblinks, views, materialized views & ref constraints.
- [Schema Migrations] - Generate deterministic schema-qualified
CREATE TABLEstatements and correctly link sequence ownership, including for trigger-emulated identity columns. - [Schema Migrations] - More reliable conversion of large packages, and more accurate package-member counts in conversion reports.
Stable release.
This is the stable release of the features introduced in 1.25.*. There are no changes since 1.25.2, but 1.26.0 marks these features as stable for all users.
- Edit Data — Edit table rows directly in an editable grid: run the Edit Data command from a table’s context menu in Object Explorer, then change cell values, add and delete rows, and save changes back to the database without writing UPDATE/INSERT/DELETE statements by hand. (#139)
- Query Placeholders with Parameter Binding — Run parameterized queries with typed placeholders and bound parameter values, integrated with the Query Plan Visualizer and an opt-in consent prompt for saving query history. (#117)
- Activity Log in Server Management — A new Activity Log pane in the server dashboard surfaces Azure control-plane operations for your server directly inside the extension.
- The query results tab now stays where you put it: re-running a query no longer forces the results pane back to the right of the editor, preserving a user-repositioned layout. (#266)
- The Schema Designer header colors now meet WCAG AA contrast requirements. (#269)
- The connection dialog no longer gets stuck in a stale-selection loop when browsing Azure resources.
- Oracle-to-PostgreSQL migration projects now use the correct settings paths for multi-schema conversions.
- Viewing a database schema no longer crashes when the server has
standard_conforming_stringsturned off. (#267) - [Schema Migrations] - Enable Object conversion that were marked as failed previously because of dependency on objects planned for future conversion and yet not converted.
- [Schema Migrations] - Deploy.sql run issues related to ordering of converted objects. Objects are now stored in order so that deploy.sql run does not throw an error and fallback objects are recovered as successful, if they are compilable post conversion.
- [Schema Migrations] - Consistent quoting of mixed-case relations and identifiers, pin session NLS formats so extracted DDL is deterministic regardless of server locale.
- [Schema Migrations] - Hardens conversion when the LLM returns malformed or empty DDLs during conversion, clamps out-of-range Oracle sequence/identity bounds
- [Schema Migrations] - Fix converson for JSON, REF CURSOR types & recover real object type for mis-typed relation dependencies.
- [Schema Migrations] - Convert wrapped Oracle objects to correct compilable declaration.
Stable release.
This is the stable release of the features introduced in 1.23.*. There are no changes since 1.23.6, but 1.24.0 marks these features as stable for all users.
- AWS RDS IAM Authentication — Connect to Amazon RDS and Aurora PostgreSQL databases using AWS RDS IAM credentials, with AWS profile and region support plus automatic credential refresh before signed tokens expire. (#211, #219)
- Visualize Durable Workflows and AI Pipelines - (Preview) Support run and definition visualizations for
pg_durableandazure_ai.pipelinescreated workflows. See the steps, failures, and timings. - Horizon DB Network Settings — Open Horizon DB network configuration from the server dashboard to manage firewall access from within the extension.
- HorizonDB Azure browse and metadata support — Browse HorizonDB clusters from the Azure connection flow. Allow fetching Azure metadata for manually entered HorizonDB hosts so dashboard Azure-management features recognize those connections.
- Agent Mode Database Tools — The bundled tools service now exposes additional DBAgent MCP tools through the PostgreSQL MCP server, giving AI assistants richer database-analysis and instruction-management capabilities.
- [Schema Migrations] — The migration setup experience now includes GA-ready UI updates, Azure Database for PostgreSQL scratch database wording, Microsoft Foundry model configuration labels, and restored enhanced-conversion engine controls.
- [Schema Migrations] — The scratch database step can verify recommended Azure Database for PostgreSQL extensions and show any missing extensions inline before schema conversion starts.
- Removed AI Model Management interface from HorizonDB provisioning. Will re-enable when it enters Public Preview stage.
- The integrated
psqlterminal command now works when PostgreSQL reports a two-part server version such as18.3, instead of failing with anInvalid Versionerror. - Deep Object Explorer refresh now recovers after dropped schemas and deleted objects instead of leaving stale nodes or failing during refresh. (#250)
- The server dashboard now probes
pg_stat_statementscorrectly on autocommit connections, avoiding false warnings that the extension could not query an installed extension. (#259) - Connection timeout failures now show clearer, consistent guidance across the connection dialog, Object Explorer, and post-connect notifications.
- Horizon DB creation failures now distinguish total deployment failures from partial follow-up failures, with raw Azure deployment details available for troubleshooting.
- Dashboard AI actions now use the correct Copilot or AI wording and launch chat correctly in Cursor.
- Saved Query History entries can now execute after the original query editor has been closed.
- Server-management actions are now gated by Azure PostgreSQL platform so unsupported management surfaces are not shown for the wrong server type.
- [Schema Migrations] — Oracle to Azure Database for PostgreSQL migration tooling is now generally available.
- [Schema Migrations] — Refined project layout, provides easier understanding and navigation
- [Schema Migrations] — Improvements in object conversion quality and more detailed reporting.
- [Schema Migrations] Scratch database extension verification now handles databases where none of the recommended extensions are installed, and changing the PostgreSQL connection no longer triggers stale verification against the previous database.
- [Schema Migrations] Review task pending badges and focus indicators now meet accessibility contrast requirements.
Stable release.
This is the stable release of the features introduced in 1.21.*. There are no changes since 1.21.2, but 1.22.0 marks these features as stable for all users.
- Performance Dashboard — Investigate database performance from the Server Dashboard with DB load charts, query activity, wait-event analysis, session health, blocking chains, shared time controls, and Azure-aware metrics.
- Object Properties — Inspect DDL and security details, including grants and row-level security policies, across all database object types from Object Explorer.
- Schema-Aware "New Query" — Right-click a schema in Object Explorer to open a new query with the appropriate
search_pathalready set, so unqualified object references resolve inside that schema without manual setup. (#238) - PostgreSQL Query Plan Node Icons — The Query Plan Visualizer now uses PostgreSQL-specific node-type icons across all views (graph, icicle, table, and source) so scan, join, and aggregate nodes are easier to identify at a glance.
- Editor Coordination with the MSSQL Extension — When both the PostgreSQL and MSSQL extensions are installed, editor ownership is now negotiated between the two, reducing duplicate toolbar actions and conflicting query execution behavior in shared editors. (#20, #67, #118, #147)
- IntelliSense Respects
search_path— Completions now honor thesearch_pathsupplied in connection options, so unqualified names suggest objects from the expected schemas first. - Horizon AI Model Management — Enable AI Model Management when creating Horizon DB resources.
- [Schema Migrations] — New enhanced conversion engine offering better DDL conversions at lesser cost & lesser time.
- [Schema Migrations] — Dynamic adaptability of conversion speed based on LLM model TPM quota.
- [Schema Migrations] — Condensed view of post-conversion "Review tasks" using grouping & categorization to reduce manual effort.
- The
@pgsqlchat participant is no longer automatically prompted by product entry points and is planned for future deprecation in favor of Agent Mode and MCP tools.
- Object scripting for partitioned tables now emits the correct
PARTITION BYclause and partition definitions instead of falling back to the default storage form. (#27) Script as Createnow includes generated column definitions such asGENERATED ALWAYS AS (...) STORED. (#248)- Deep refresh now recovers when the selected Object Explorer item has already been deleted, instead of failing with an index error. (#250)
- Query execution now works for SQL files whose paths contain spaces, percent signs, brackets, backticks, or encoded path segments.
- Fixed a hang during Docker container creation caused by a task-wrapper race condition. (#252)
- "Analyze with Copilot" from Dashboard Metrics now passes the correct context to the tool, resolving errors that previously occurred during execution.
Stable release.
This is the stable release of the features introduced in 1.19.0. There are no changes since 1.19.0, but 1.20.0 marks these features as stable for all users.
- Azure HorizonDB Provisioning — Create and configure Azure HorizonDB clusters directly from the extension, without switching to the Azure Portal. HorizonDB is currently in Private Preview, learn more here.
- Server Restore / Clone — Restore or clone Azure Database for PostgreSQL Flexible Server instances directly from the server dashboard. Choose a full backup or a specific point-in-time to recover from, and spin up a new server without leaving VS Code.
- Improved Object Explorer Refresh — Refreshing a node now reliably picks up all additions and removals throughout its entire subtree, so new database objects appear and deleted ones disappear without needing to disconnect and reconnect. (#64, #152, #199)
- Multi-Source Connection Settings — Connection profiles can now be saved to your user settings, workspace, or folder. Save a profile to your workspace settings to check it into source control alongside your code — giving every team member the right database connections whenever they open the project. A scope selector makes it clear where each new profile will be saved, and duplicate profiles across scopes are automatically removed. (#191, #133, #221)
- Apache AGE Graph Visualization Improvements — Improved layout, controls, and usability of the Apache AGE graph visualization panel.
- Copilot SQL Auto-Attach — Added an auto-attach setting to automatically attach SQL context to Copilot conversations. Improved modal prompt and tool guidance for SQL attach workflows. (#233)
- Smarter Query Plan Copilot Recommendations — Copilot analysis of query plans now uses a verification protocol for more reliable and actionable optimization suggestions. (#234)
- Static Query Plan Summarization — Query plans can now include static summarization to surface high-level plan characteristics without a full Copilot analysis.
- [Schema Migrations] Support for Microsoft Entra Authentication for Azure OpenAI Endpoint.
DROP FUNCTIONscript generation produced malformed SQL in some cases (#236)- Foreign tables did not appear in IntelliSense completions (#197)
- "Script as Create" on a materialized view always generated the DDL for the first materialized view in the schema, regardless of which object was selected (#237)
START TRANSACTIONwas executed incorrectly, causing unexpected transaction state (#229)- DDL generation for objects using built-in trigger functions (e.g.
tsvector_update_trigger) produced unquoted arguments (#227) - Exporting query results as JSON double-encoded JSON/JSONB column values (#235)
- "Enable richer experiences" command was missing from the Command Palette; disambiguated palette labels for related commands (#232)
pgsql_query_planMCP toolfilterTypeparameter was not correctly applied in some cases (233)- Connecting via a SQL file before opening the PostgreSQL panel could leave Object Explorer showing only the active server; saved connections are now correctly restored in this path (#242)
- Schema visualizer legend now uses less vertical screen space
- [Schema Migrations] Hotfix patches addressing schema migration issues
Stable release.
This is the stable release of the features introduced in 1.17.0. There are no changes since 1.17.0, but 1.18.0 marks these features as stable for all users.
- Query Plan Visualization Explore PostgreSQL EXPLAIN output in four synchronized views: an interactive node graph, icicle chart, sortable table, and raw source. Color-coded severity groups expose performance bottlenecks at a glance, and GitHub Copilot integration provides AI-assisted analysis and optimization suggestions. Launch from the query editor toolbar, the Query Results panel, or the Command Palette. (read more)
- Object Explorer Search Find database objects by name without expanding the Object Explorer tree. Search across connections, databases, and schemas; filter by object type (tables, views, functions, sequences, and more) or schema name; and click any result to navigate directly to it in the tree. (read more)
- Graph Visualization Apache AGE graph query results are automatically detected and rendered as an interactive node-edge graph directly in the results pane, with per-node callouts, zoom and pan controls, export support, and theme-aware styling. (read more)
- MCP Server — The extension registers a Model Context Protocol (MCP) server with VS Code, enabling AI assistants to discover and interact with your PostgreSQL databases through a standardized tool interface.
- Azure Backup Management — List, create, and delete on-demand backups and configure retention periods for Azure Database for PostgreSQL Flexible Servers directly from VS Code, without switching to the Azure Portal.
- Azure Server Logs — Configure log capture settings, set retention periods, and download server and upgrade logs directly from the Server Dashboard for Azure Database for PostgreSQL Flexible Servers.
- [Schema Migrations] Migration service version updated to 2.0.0
- [Schema Migrations] Migration engine now supports GPT5.2 model
- [Schema Migrations] Timeout thresholds for agent conversation and OpenAPI connection
- [Schema Migrations] Object-level conversion now uses JSON-based chunking for more reliable handling of large schemas and cyclic table dependencies.
- The
pgsql_list_serversLanguage Model Tool (LMT) has been renamed topgsql_list_connection_profilesto align with the MCP tool name used in templated prompts. Any custom prompts or integrations referencing the oldpgsql_list_serverstool name must be updated.
- Server parameters multi-select dropdowns now correctly display and match selected values, including case-insensitive comparison against server-returned values
- Docker container creation now validates that a password is provided before starting the container, preventing post-start connection failures
- IntelliSense completions no longer fail to refresh for partitioned tables
- JSON Schema
$refresolution warning no longer appears when opening JSON files (#223) - Tool-initiated transactions are rolled back automatically on failure, eliminating the need to manually issue ROLLBACK after a query error (#166)
Stable release.
This is the stable release of the features introduced in 1.15.0. There are no changes since 1.15.0, but 1.16.0 marks these features as stable for all users.
- The extension is now available on Windows 11 ARM64 devices under Prism emulation (#82)
- Create new Azure Database for PostgreSQL Flexible Server instances directly from the extension
- Manage Azure Database for PostgreSQL Flexible Server firewall rules, server parameters, and server states directly from the extension
- Schema filtering for schema visualization: select specific schemas to include or exclude when visualizing database schemas, accessible from Object Explorer nodes or directly in the visualization tool (#49)
- SSL connections now support custom file and "system"
sslrootcertvalues, pairing "system" selections withverify-fullsslmode - UI elements in Object Explorer and Query Editor will indicate when an active connection is lost
- [Schema Migrations] Additional localization language entries
- [Schema Migrations] Support for Oracle Thick Client Connection
- [Schema Migrations] Best Effort conversion when primary conversion reaches messages limit
- [Schema Migrations] Handle cyclic dependencies in schema objects
- [Schema Migrations] Display success metrics for programmable/non-programmable objects
- Closing query editors returns underlying database connections to the pool for reuse instead of exhausting available connections (#178)
- Table results filter panel layout, sizing, and behavior improvements to prevent clipping and improve usability across different panel sizes (#189)
- [Schema Migrations] Correctly handle sequence dependencies extraction
- [Schema Migrations] Topological sorting fix in chunking logic to handle cyclic dependencies
- [Schema Migrations] Fix conversion % displayed in report for chunk failures
- [Schema Migrations] Fix connection to Oracle DB using Service ID
- [Schema Migrations] Convert unique indexes as is and not as primary index
Stable release.
This is the stable release of the features introduced in 1.13.*. There are no changes since 1.13.0, but 1.14.0 marks these features as stable for all users.
- Improved accessibility for Metrics Dashboard with keyboard navigation support for data points and legend controls
- Schema migrations handle appropriate naming of constrains in the coverted DDL statements
- Schema migrations handle conversion of partitions for Oracle to PostgreSQL
- Entra ID authentication now supports Personal Microsoft Accounts (MSA) in addition to work/school accounts (#183)
- Connection profiles with duplicate server names, database, and credentials can now be saved, enabling more SSH tunneling and jump host scenarios (#48, #175)
- Schema migration correctly handle trigger dependencies which caused extraction failures on some schemas
- Additional localization language updates
- Use new Copilot Chat extension to register @pgsql chat participant, restores "Chat with database" functionality (#193)
Stable release.
This is the stable release of the features introduced in 1.11.*. There are no changes since 1.11.4, but 1.12.0 marks these features as stable for all users.
Notably, this release makes the Oracle to Azure Database for PostgreSQL migration tooling available for all users in Preview. This AI-powered feature helps you migrate Oracle database schemas and application code to PostgreSQL. Learn more.
- [Preview] Oracle to Azure Database for PostgreSQL schema and application conversion (read more)
- macOS arm64 builds no longer require Rosetta 2 emulation
- Prevent corrupt Entra accounts from being saved in connection profiles ([#164])
- Database schema names beginning with
pgare no longer listed under the "System Schemas" path in Object Explorer
- Feedback prompts are not shown when VS Code setting
telemetry.feedback.enabledis set tofalse
- Experimental support for Start/Stop/Restart server operations on Azure Database for PostgreSQL Flexible Servers (
pgsql.azureServer.preview.enabledsetting)
- The extension now includes all platform-specific dependencies and is published per supported platform; no post-install downloads are required. Installs should work for network-restricted environments.
- Updates to improve accessibility and language localization
Stable release.
This is the stable release of the features introduced in 1.9.*. There are no changes since 1.9.1, but 1.10.0 marks these features as stable for all users.
- Stabilize memory consumption in long-running dashboard sessions
- Metric chart x-axis now trims to available data range after user machine sleep or network interruptions
- System metrics normalize rate calculations after user machine wakes from sleep
- Handle Azure API failures during metrics polling
- Server dashboard offering high-level metadata plus real-time and historical performance metrics for PostgreSQL servers, providing visibility into server health and workload patterns (historical data available for Azure Database for PostgreSQL Flexible Server). See more details here.
- GitHub Copilot Chat integration for server performance metrics: use natural language to inspect trends, identify bottlenecks, and generate diagnostic SQL.
- Keybinding for "Run Current Statement" in the Query Editor (default:
Ctrl+Shift+Enter) executes the statement under the cursor without requiring a selection (#121, #103) - Dragging an Object Explorer entity into an editor now inserts a correctly double-quoted identifier (#126)
- Allow database connections via socket file paths (#34)
- Client tools dependency installation is now atomic to prevent partial or corrupted installs (#144, #138, #128)
- "Explain Analyze" toolbar toggle now preserves its correct state for both saved and unsaved SQL files (#145)
- Integrated
psqlshell now supports custom binary paths containing spaces on Windows (#148) - Entra auth tokens regenerate when the selected Entra account or tenant changes in the connection dialog
- Removed inadvertent logging of sensitive information in extension logs (#102)
- Correct datatype mapping for
oidvalues exceeding the Python signed integer limit (#129)
- Improved connection retry logic and resilience during long-running sessions and transient network interruptions
- Removed deprecated or unused dependencies and upgraded remaining packages
Stable release.
This is the stable release of the features introduced in 1.7.*. There are no changes since 1.7.1, but 1.8.0 marks these features as stable for all users.
- SSH connection configuration includes ssh-agent support for private key authentication (#123)
Pre-release version
- SSH connection parameters can now be configured in the Advanced section of the connection dialog. The extension will create an SSH tunnel using the provided credentials, enabling database connections to private networks (#54)
- Explicit option for "No Password" authentication type to reduce confusion between missing and intentionally omitted passwords.
- Selecting Entra Authentication type in the Connection String dialog for new connections does not populate default Entra Username or Tenant
- "Script as ..." command on an Object Explorer node with an expired Entra token fails instead of refreshing the token
- New connection attempts that used an incorrect Entra token (from a wrong Entra ID or tenant selection in the UI) will fail even after correcting the settings
- Connection attempts that fail without error messages are treated as successful by the Object Explorer, but still results in a failed session
- Unicode characters were incorrectly escaped when embedded in a PostgreSQL array type (#70)
- PostgreSQL array values were serialized and displayed as JSON arrays instead of PostgreSQL syntax (#70)
- When using "Connect with VS Code" from Azure Portal, if the profile already exists, the existing profile dialog opens instead of creating a duplicate. Clicking Connect will now automatically connect using the existing profile. (#79, #38)
Stable release.
This is the stable release of the features introduced in 1.5.0. There are no changes since 1.5.0, but 1.6.0 marks these features as stable for all users.
Pre-release version
- Support for selecting Entra Tenant when using Entra ID authentication for PostgreSQL connections (#17)
- Support for providing a custom user name or Security Group name when using Entra ID authentication for PostgreSQL connections (#30)
- Improved process and thread management for the PostgreSQL Tools Service, including better handling of service restarts and process terminations
- Validate file integrity when downloading PostgreSQL Tools Service archive
- Support for Docker
platformargument when using custom images for new Docker PostgreSQL creation. This is required for ARM64 architecture support on some images like PostGIS. - Improved documentation for supported platforms and architectures in the README
- IntelliSense stops working after saving SQL file, or when opening a saved SQL file (#68)
- PostgreSQL connection string parsing errors, including issues with underscore characters and connection strings without passwords (#69)
- Entra ID token fetching issues and account validation scenarios
- Extension startup crashes caused by invalid or corrupted connection profiles (now validated and ignored on startup)
- @pgsql Copilot Chat participant is enabled by default. If GH Copilot Chat is installed, it can be used for chat interactions with your PostgreSQL databases. (#58, #66)
- Improved layout of command buttons in Query History window
- Update extension license terms
- Broken relative links in bundled README
Pre-release version
- Update extension metadata for rendering in VS Code Marketplace
Public preview release.
- Migrate previous
ms-ossdata.vscode-postgresqlextension settings to the new settings on startup
- Handle cases of unexpected EOF streams in the PostgreSQL Tools Service
Initial release to Marketplace for testing public preview.