Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex MPP Analytics for PostgreSQL
  • Getting started
    • All guides
      • Information about existing clusters
      • Creating a cluster
      • Expanding a cluster
      • Editing the cluster configuration
      • Updating cluster settings
      • Stopping and starting a cluster
      • Managing backups
      • Managing cluster access
      • Yandex MPP Analytics for PostgreSQL version upgrade
      • Maintenance
      • Deleting a cluster
    • Connecting to an external file server (gpfdist)
    • Auxiliary utilities
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Viewing a list of available versions
  • Before a version upgrade
  • Upgrading a cluster
  1. Step-by-step guides
  2. Clusters
  3. Yandex MPP Analytics for PostgreSQL version upgrade

Yandex MPP Analytics for PostgreSQL version upgrade

Written by
Yandex Cloud
Updated at July 23, 2026
View in Markdown
  • Viewing a list of available versions
  • Before a version upgrade
  • Upgrading a cluster

You can change the database version of your Yandex MPP Analytics for PostgreSQL cluster.

Note

Greenplum® upgrades from version 6.28 to 6.29 are supported.

The following upgrades are not supported:

  • Manual upgrades between Greenplum® patch versions, e.g., from 6.29.1 to 6.29.2. Such upgrades are performed automatically during maintenance.
  • Apache Cloudberry™ version upgrades.
  • Migrations between Greenplum® and Apache Cloudberry™.

To learn about upgrades within the same version and host maintenance, see Maintenance.

Viewing a list of available versionsViewing a list of available versions

Management console
REST API
gRPC API

In the management console, open the Yandex MPP Analytics for PostgreSQL cluster create or update page. You can view the list in the Version field.

  1. Get an IAM token for API authentication and put it into an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Call the Versions.List method, e.g., via the following cURL request:

    curl \
        --request GET \
        --header "Authorization: Bearer $IAM_TOKEN" \
        --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/versions'
    
  3. Check the server response to make sure your request was successful.

  1. Get an IAM token for API authentication and put it into an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume that the repository contents reside in the ~/cloudapi/ directory.

  3. Call the VersionsService.List method, e.g., via the following gRPCurl request:

    grpcurl \
        -format json \
        -import-path ~/cloudapi/ \
        -import-path ~/cloudapi/third_party/googleapis/ \
        -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/versions_service.proto \
        -rpc-header "Authorization: Bearer $IAM_TOKEN" \
        mdb.api.cloud.yandex.net:443 \
        yandex.cloud.mdb.greenplum.v1.VersionsService.List
    
  4. Check the server response to make sure your request was successful.

Before a version upgradeBefore a version upgrade

Make sure the upgrade will not disrupt your applications:

  1. Learn how upgrades may affect your applications:

    • Greenplum® release notes
    • Apache Cloudberry™ release notes
  2. Try upgrading a test cluster. You can deploy it from a backup of the main cluster, if Yandex MPP Analytics for PostgreSQL supports the database version in the backup.

  3. Back up your main cluster before upgrading.

Upgrading a clusterUpgrading a cluster

Alert

Once your database version is upgraded, you cannot revert the cluster to the previous version.

Management console
Terraform
REST API
gRPC API
  1. In the management console, navigate to the relevant folder.
  2. Navigate to Yandex MPP Analytics for PostgreSQL.
  3. In the cluster row, click and select Edit.
  4. Select the new version number in the Version field.
  5. Click Save.
  1. Open the current Terraform configuration file with the infrastructure plan.

    For information on how to create this file, see Creating a cluster Yandex MPP Analytics for PostgreSQL.

  2. In the config section of the Yandex MPP Analytics for PostgreSQL cluster, add the version field (the database version) or update its value if it already exists:

    resource "yandex_mdb_greenplum_cluster" "<cluster_name>" {
      ...
      version = "<version>"
    }
    
  3. Make sure the settings are correct.

    1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

    2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

  4. Confirm updating the resources.

    1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply
        
      2. Confirm updating the resources.

      3. Wait for the operation to complete.

For more information, see this Terraform provider guide.

  1. Get an IAM token for API authentication and put it into an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Call the Cluster.update method, e.g., via the following cURL request:

    Warning

    The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the updateMask parameter as a single comma-separated string.

    curl \
        --request PATCH \
        --header "Authorization: Bearer $IAM_TOKEN" \
        --header "Content-Type: application/json" \
        -url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/clusters/<cluster_ID>' \
        --data '{
                  "updateMask": "config.version",
                  "config": {
                    "version": "<version>"
                  }
                }'
    

    Where:

    • updateMask: Comma-separated string of settings to update.

      Here, we only specified a single setting, config.version.

    • config.version: Target database version.

    You can get the cluster ID with the list of clusters in the folder.

  3. View the server response to make sure your request was successful.

  1. Get an IAM token for API authentication and put it into an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume that the repository contents reside in the ~/cloudapi/ directory.

  3. Call the ClusterService/Update method, e.g., via the following gRPCurl request:

    Warning

    The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the update_mask parameter as an array of paths[] strings.

    Format for listing settings
    "update_mask": {
        "paths": [
            "<setting_1>",
            "<setting_2>",
            ...
            "<setting_N>"
        ]
    }
    
    grpcurl \
        -format json \
        -import-path ~/cloudapi/ \
        -import-path ~/cloudapi/third_party/googleapis/ \
        -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/cluster_service.proto \
        -rpc-header "Authorization: Bearer $IAM_TOKEN" \
        -d '{
              "cluster_id": "<cluster_ID>",
              "update_mask": {
                "paths": [
                  "config.version"
                ]
              },
              "config": {
                "version": "<version>"
              }
            }' \
        mdb.api.cloud.yandex.net:443 \
        yandex.cloud.mdb.greenplum.v1.ClusterService.Update
    

    Where:

    • update_mask: List of settings to update as an array of strings (paths[]).

      Here, we only specified a single setting, config.version.

    • config.version: Target database version.

    You can get the cluster ID with the list of clusters in the folder.

  4. Check the server response to make sure your request was successful.

Was the article helpful?

Previous
Managing cluster access
Next
Maintenance
© 2026 Direct Cursus Technology L.L.C.