You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/postgresql/configure-maintain/overview-postgres-choose-server-options.md
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
---
2
-
title: Choose hosting type
2
+
title: Choose Hosting Type
3
3
description: Provides guidelines for choosing the right Azure Database for PostgreSQL flexible server instance hosting option.
4
4
author: varun-dhawan
5
5
ms.author: varundhawan
6
6
ms.reviewer: maghan
7
-
ms.date: 04/27/2024
7
+
ms.date: 05/05/2026
8
8
ms.service: azure-database-postgresql
9
9
ms.subservice: configuration
10
10
ms.topic: overview
11
11
ms.custom:
12
12
- mvc
13
13
---
14
14
15
-
# Choose the right Azure Database for PostgreSQL hosting option in Azure
15
+
# Choose the right Azure Database for PostgreSQL hosting option in Azure
16
16
17
17
With Azure, your PostgreSQL workloads can run in a hosted virtual machine infrastructure as a service (IaaS) or as a hosted platform as a service (PaaS). PaaS has multiple deployment options, each with multiple service tiers. When you choose between IaaS and PaaS, you must decide if you want to manage your database, apply patches, and make backups, or if you want to delegate these operations to Azure.
18
18
@@ -23,18 +23,18 @@ When making your decision, consider the following option in PaaS or alternativel
23
23
24
24
The main differences between these options are listed in the following table:
25
25
26
-
|**Attribute**|**Postgres on Azure VMs**|**Azure Database for PostgreSQL as PaaS**|
|**OS and PostgreSQL patching**| - Customer managed | Automatic with optional customer managed window|
30
-
|**High availability**| - Customers architect, implement, test, and maintain high availability. Capabilities might include clustering, replication etc. | Built-in|
31
-
|**Zone Redundancy**| - Azure VMs can be set up to run in different availability zones. For an on-premises solution, customers must create, manage, and maintain their own secondary data center. | Yes|
|**Backup and Restore**| - Customer Managed | Built-in with user configuration on zone-redundant storage|
34
-
|**Monitoring Database Operations**| - Customer Managed | All offer customers the ability to set alerts on the database operation and act upon reaching thresholds |
35
-
|**Advanced Threat Protection**| - Customers must build this protection for themselves. | Not available during Preview|
|**OS and PostgreSQL patching**| - Customer managed | Automatic with optional customer managed window |
30
+
|**High availability**| - Customers architect, implement, test, and maintain high availability. Capabilities might include clustering, replication etc. | Built-in |
31
+
|**Zone Redundancy**| - Azure VMs can be set up to run in different availability zones. For an on-premises solution, customers must create, manage, and maintain their own secondary data center. | Yes |
|**Backup and Restore**| - Customer Managed | Built-in with user configuration on zone-redundant storage |
34
+
|**Monitoring Database Operations**| - Customer Managed | All offer customers the ability to set alerts on the database operation and act upon reaching thresholds |
35
+
|**Advanced Threat Protection**| - Customers must build this protection for themselves. | Not available during Preview |
@@ -44,7 +44,7 @@ TCO is often the primary consideration that determines the best solution for hos
44
44
45
45
Azure Database for PostgreSQL is currently available as a service in several tiers with different prices for resources. All resources are billed hourly at a fixed rate. For the latest information on the currently supported service tiers, compute sizes, and storage amounts, see [pricing page](https://azure.microsoft.com/pricing/details/postgresql/server/) You can dynamically adjust service tiers and compute sizes to match your application's varied throughput needs. You're billed for outgoing Internet traffic at regular [data transfer rates](https://azure.microsoft.com/pricing/details/data-transfers/).
46
46
47
-
With Azure Database for PostgreSQL, Microsoft automatically configures, patches, and upgrades the database software. These automated actions reduce your administration costs. Also, Azure Database for PostgreSQL has [automated backup-link]() capabilities. These capabilities help you achieve significant cost savings, especially when you have a large number of databases. In contrast, with PostgreSQL on Azure VMs you can choose and run any PostgreSQL version. However, you need to pay for the provisioned VM, storage cost associated with the data, backup, monitoring data and log storage and the costs for the specific PostgreSQL license type used (if any).
47
+
With Azure Database for PostgreSQL, Microsoft automatically configures, patches, and upgrades the database software. These automated actions reduce your administration costs. Also, Azure Database for PostgreSQL has automated backup capabilities. These capabilities help you achieve significant cost savings, especially when you have a large number of databases. In contrast, with PostgreSQL on Azure VMs you can choose and run any PostgreSQL version. However, you need to pay for the provisioned VM, storage cost associated with the data, backup, monitoring data and log storage and the costs for the specific PostgreSQL license type used (if any).
48
48
49
49
Azure Database for PostgreSQL provides built-in high availability at the zonal-level (within an AZ) for any kind of node-level interruption while still maintaining the [SLA guarantee](https://azure.microsoft.com/support/legal/sla/postgresql/v1_2/) for the service. Azure Database for PostgreSQL provides [uptime SLAs](https://azure.microsoft.com/support/legal/sla/postgresql/v1_2/) with and without zone-redundant configuration. However, for database high availability within VMs, you use the high availability options like [Streaming Replication](https://www.postgresql.org/docs/current/warm-standby.html#STREAMING-REPLICATION) that are available on a PostgreSQL database. Using a supported high availability option doesn't provide another SLA. But it does let you achieve greater than 99.99% database availability at more cost and administrative overhead.
50
50
@@ -55,7 +55,7 @@ For more information on pricing, see the following articles:
55
55
56
56
## Administration
57
57
58
-
For many businesses, the decision to transition to a cloud service is as much about offloading complexity of administration as it is about cost.
58
+
For many businesses, the decision to transition to a cloud service is as much about offloading complexity of administration as it's about cost.
59
59
60
60
With IaaS, Microsoft:
61
61
@@ -84,13 +84,13 @@ Additionally, configuring high availability to another data center requires mini
84
84
85
85
- With PostgreSQL on Azure VMs, you have full control over the operating system and the PostgreSQL server instance configuration. With a VM, you decide when to update or upgrade the operating system and database software and what patches to apply. You also decide when to install any other software such as an antivirus application. Some automated features are provided to greatly simplify patching, backup, and high availability. You can control the size of the VM, the number of disks, and their storage configurations. For more information, see [Virtual machine and cloud service sizes for Azure](/azure/virtual-machines/sizes).
86
86
87
-
## Time to move to Azure Database for PostgreSQL (PaaS)
87
+
## Time to move to Azure Database for PostgreSQL (PaaS)
88
88
89
89
- Azure Database for PostgreSQL is the right solution for cloud-designed applications when developer productivity and fast time to market for new solutions are critical. With programmatic functionality that is like DBA, the service is suitable for cloud architects and developers because it lowers the need for managing the underlying operating system and database.
90
90
91
91
- When you want to avoid the time and expense of acquiring new on-premises hardware, PostgreSQL on Azure VMs is the right solution for applications that require a granular control and customization of PostgreSQL engine not supported by the service or requiring access of the underlying OS.
92
92
93
93
## Related content
94
94
95
-
-[Azure Database for PostgreSQL pricing](https://azure.microsoft.com/pricing/details/postgresql/server/).
96
-
-[Create an Azure Database for PostgreSQL](quickstart-create-server.md).
95
+
-[Azure Database for PostgreSQL pricing](https://azure.microsoft.com/pricing/details/postgresql/server/)
96
+
-[Quickstart: Create an Azure Database for PostgreSQL flexible server](quickstart-create-server.md)
Copy file name to clipboardExpand all lines: articles/postgresql/developer/vs-code-extension/vs-code-github-copilot.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
-
title: "Quickstart: Guide for GitHub Copilot Feature for Visual Studio Code PostgreSQL Extension"
3
-
description: Learn how to use the GitHub Copilot integration in the PostgreSQL extension for Visual Studio Code.
2
+
title: "Quickstart: Guide for GitHub Copilot Feature for Visual Studio Code PostgreSQL Extension in Azure HorizonDB"
3
+
description: Learn how to use the GitHub Copilot integration in the PostgreSQL extension for Visual Studio Code in Azure HorizonDB.
4
4
author: swarathmika
5
5
ms.author: skakivaya
6
6
ms.reviewer: maghan
7
-
ms.date: 01/09/2026
7
+
ms.date: 05/05/2026
8
8
ms.service: azure-database-postgresql
9
9
ms.topic: quickstart
10
10
ms.collection:
@@ -17,7 +17,7 @@ ms.custom:
17
17
ai-usage: ai-assisted
18
18
---
19
19
20
-
# Quickstart: Configure GitHub Copilot for PostgreSQL extension in Visual Studio Code
20
+
# Quickstart: Configure GitHub Copilot for PostgreSQL extension in Visual Studio Code in Azure HorizonDB
21
21
22
22
The PostgreSQL extension for Visual Studio Code now includes GitHub Copilot integration, enhancing your database workflows with AI-assisted development. Copilot accesses contextual information from your live connection, once connected to a PostgreSQL database. This access enables the `@pgsql` Copilot chat participant to generate accurate, schema-aware SQL queries and insights, streamlining development and minimizing context-switching within Visual Studio Code.
23
23
@@ -46,7 +46,7 @@ These tools and resources help you follow along with this article and make the m
46
46
47
47
1. Make sure you have a GitHub account and an active GitHub Copilot subscription:
1. In Visual Studio Code, select the **Account** icon and choose **Sign in with GitHub to use GitHub Copilot**.
@@ -71,7 +71,9 @@ Try a prompt like:
71
71
72
72
1. Copilot responds with a detailed description of your schema's tables.
73
73
74
-
## Using read and write capabilities
74
+
<aid="using-read-and-write-capabilities"></a>
75
+
76
+
## Use read and write capabilities
75
77
76
78
The GitHub Copilot integration for the PostgreSQL extension in Visual Studio Code enables seamless read and write capabilities. With this integration, you can interact with your databases more efficiently. By using AI-powered suggestions, you can perform tasks such as querying data, modifying schemas, and updating records directly from the editor. This feature simplifies complex operations, reduces manual effort, and enhances productivity while maintaining accuracy and context-awareness.
77
79
@@ -98,7 +100,9 @@ Then Copilot asks for confirmation:
98
100
@pgsql Yes, I confirm
99
101
```
100
102
101
-
## Using context menu options
103
+
<aid="using-context-menu-options"></a>
104
+
105
+
## Use context menu options
102
106
103
107
- You can select SQL code in the editor and right-click to access GitHub Copilot context menu options like **Explain Query**, **Rewrite Query**, or **Analyze Query Performance**.
104
108
@@ -162,6 +166,6 @@ For bugs, feature requests, and issues, use the built-in feedback tool in Visual
162
166
163
167
## Related content
164
168
165
-
-[What is the PostgreSQL extension for Visual Studio Code?](vs-code-overview.md)
169
+
-[What is the PostgreSQL extension for Visual Studio Code in Azure HorizonDB?](vs-code-overview.md)
166
170
-[Quickstart: Connect and query a database with the PostgreSQL extension for Visual Studio Code](vs-code-connect.md)
167
171
-[PostgreSQL extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-ossdata.vscode-pgsql)
Copy file name to clipboardExpand all lines: articles/postgresql/developer/vs-code-extension/vs-code-overview.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
-
title: What Is the PostgreSQL Extension for Visual Studio Code?
3
-
description: Overview of the PostgreSQL extension for Visual Studio Code.
2
+
title: What Is the PostgreSQL Extension for Visual Studio Code in Azure HorizonDB?
3
+
description: Overview of the PostgreSQL extension for Visual Studio Code in Azure HorizonDB.
4
4
author: swarathmika
5
5
ms.author: skakivaya
6
6
ms.reviewer: maghan
7
-
ms.date: 01/09/2026
7
+
ms.date: 05/05/2026
8
8
ms.service: azure-database-postgresql
9
9
ms.subservice: extensions
10
10
ms.topic: overview
@@ -14,7 +14,7 @@ ai-usage: ai-assisted
14
14
# customer intent: As a user, I want to understand what the PostgreSQL extension for VS Code is and how I can use it with an Azure Database for PostgreSQL flexible server instance.
15
15
---
16
16
17
-
# What is the PostgreSQL extension for Visual Studio Code?
17
+
# What is the PostgreSQL extension for Visual Studio Code in Azure HorizonDB?
18
18
19
19
The PostgreSQL extension for Visual Studio Code is a feature-rich tool designed to simplify PostgreSQL database management and development. This extension empowers developers to connect to PostgreSQL databases, write and execute queries, and manage database objects without leaving the Visual Studio Code environment. This extension revolutionizes the PostgreSQL development workflow by introducing comprehensive functionality, intuitive UI design, and seamless integration with cloud platforms such as Azure Database for PostgreSQL.
20
20
@@ -66,17 +66,19 @@ The Results Viewer enables you to interact with query results through features s
66
66
67
67
### Apache AGE Graph Visualization
68
68
69
-
The Apache AGE Graph Visualizer lets you run Apache AGE Cypher queries and explore the results as an interactive node-edge graph. The extension automatically detects graph query results and renders them in a visual explorer with per-node callouts, zoom and pan controls, export support, and theme-aware styling.
69
+
The Apache AGE Graph Visualizer lets you run Apache AGE Cipher queries and explore the results as an interactive node-edge graph. The extension automatically detects graph query results and renders them in a visual explorer with per-node callouts, zoom and pan controls, export support, and theme-aware styling.
70
70
71
71
To render results in the graph visualizer, your queries must meet the following requirements:
72
72
-**Return full objects, not scalar properties** - The graph visualizer needs complete vertex and edge objects. Queries that extract scalar properties (`RETURN p.name, p.title`) return plain text values and won't render in the visualizer. Instead of returning properties, return the full objects and name the relationship variable:
73
+
73
74
```sql
74
75
SELECT*FROM cypher('my_graph', $$
75
76
MATCH (a:Product)-[r:BOUGHT_TOGETHER]->(b:Product)
76
77
RETURN a, r, b
77
78
$$) AS (a agtype, r agtype, b agtype);
78
79
```
79
80
-**Set `disp_label` for meaningful node text** - Without `disp_label`, nodes display internal IDs. Set this property so the visualizer shows useful labels:
81
+
80
82
```sql
81
83
SELECT*FROM cypher('my_graph', $$
82
84
MATCH (a:Product)-[r:BOUGHT_TOGETHER]->(b:Product)
@@ -86,6 +88,7 @@ To render results in the graph visualizer, your queries must meet the following
86
88
$$) AS (a agtype, r agtype, b agtype);
87
89
```
88
90
-**Match output columns to returned objects** - The wrapper `AS (...)` clause must have one column per returned object. For multi-hop queries, include every intermediate node and edge:
91
+
89
92
```sql
90
93
SELECT*FROM cypher('my_graph', $$
91
94
MATCH (a:Product)-[r1:BOUGHT_TOGETHER]->(mid:Product)-[r2:BOUGHT_TOGETHER]->(b:Product)
@@ -120,5 +123,5 @@ For bugs, feature requests, and issues, use the built-in feedback tool in Visual
120
123
## Related content
121
124
122
125
-[Quickstart: Connect and query a database with the PostgreSQL extension for Visual Studio Code](vs-code-connect.md)
123
-
-[Quickstart: Configure GitHub Copilot for PostgreSQL extension in Visual Studio Code](vs-code-github-copilot.md)
126
+
-[Quickstart: Configure GitHub Copilot for PostgreSQL extension in Visual Studio Code in Azure HorizonDB](vs-code-github-copilot.md)
124
127
-[PostgreSQL extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-ossdata.vscode-pgsql)
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments