Microsoft presented a public preview of a PostgreSQL extension for Visual Studio Code that brought database administration and query development into the code editor. The company’s announcement, originally posted on May 19 and updated on the event date, positioned the extension as a unified workspace for application code and PostgreSQL tasks.
The preview allowed developers to manage database objects and execute queries without switching to a separate database application. It included context-aware IntelliSense and SQL formatting to assist with drafting and reviewing queries. Microsoft also integrated a PostgreSQL-focused GitHub Copilot chat agent, invoked through `@pgsql`, which could use database and workspace context to provide assistance and handle multi-step tasks.
That Copilot component required users to have both the GitHub Copilot and GitHub Copilot Chat extensions installed. After signing into a GitHub account, a developer could call the PostgreSQL agent from the VS Code chat interface and interact with a connected database. The database tooling itself was therefore part of the PostgreSQL extension, while the conversational features depended on Microsoft’s separate Copilot setup.
Connection management was another part of the preview. Microsoft said its Connection Manager was intended to shorten initial setup, while integration with Microsoft Entra ID provided centralized identity and access controls. Users could browse Azure Database for PostgreSQL instances, and the extension included deeper integration with that managed service. Microsoft also described support for managing database objects, running queries and deploying instances from within VS Code.
The company offered the preview through the Visual Studio Code Extensions Marketplace. Its listing used the identifier `ms-ossdata.vscode-pgsql`; Microsoft instructed users to search for PostgreSQL and select the preview extension marked with a blue elephant. The release was intended for evaluation, and the announcement directed users to a built-in feedback tool for feature requests and problem reports.
Microsoft also addressed the license wording attached to the initial preview. It said the standard preview language would be updated, with the stated aim of making the extension broadly available to PostgreSQL users. The post did not set out a timetable for that change, so the license note remained an item for prospective users to review while assessing the preview.
The release reflected an effort to reduce the separation between writing application code and working with its database. Instead of moving among an editor, a query tool and cloud-management interfaces, developers could perform more of those activities in one environment. The value of that approach depended on the preview’s reliability and fit with existing workflows, which was why Microsoft sought feedback before a later release stage.
As a preview rather than a final product, the extension represented a testable direction for Microsoft’s PostgreSQL tooling. Its defining elements were the combination of conventional database controls, Azure connections, query assistance and an optional context-aware Copilot agent inside VS Code.
