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 Cloud Stackland
  • What's new
  • Installation
    • All tutorials
    • Installing Stackland on Yandex BareMetal
    • Installing Stackland on Yandex BareMetal via PXE
    • Installing Stackland on Yandex Cloud VMs
    • Setting up external access to a pod in a cluster
    • All guides
        • Creating a PostgreSQL cluster
        • Updating cluster settings
        • Creating a user
        • Updating a user
        • Deleting a user
        • Create database
        • Update database
        • Deleting a database
        • Performance diagnostics
        • Create a backup
        • Recovering a cluster
        • Deleting a cluster
    • Projects
    • Resource model
    • Scaling a cluster
  • Access management
  • Pricing policy
  • Diagnostics and troubleshooting
  1. Step-by-step guides
  2. Databases
  3. Managed Service for PostgreSQL
  4. Create database

Creating a PostgreSQL database

Written by
Yandex Cloud
Updated at July 24, 2026
View in Markdown

If you have a PostgreSQL cluster in your project, you can create a database in it. Use a PostgresqlDatabase resource to define the database. Set the database owner using the spec.owner field. It must match an existing PostgreSQL role. For details, see Creating a PostgreSQL user.

Using the CLIUsing the CLI

  1. Create the PostgresqlDatabase resource file, e.g., using the touch postgresqldatabase.yaml command.

  2. Open the file and paste the configuration below into it:

    Minimum configuration
    libc locale
    ICU locale
    builtin locale
    Schemas
    apiVersion: postgresql.stackland.yandex.cloud/v1alpha1
    kind: PostgresqlDatabase
    metadata:
      name: test-cluster-test-database
    spec:
      cluster: test-cluster # Name of PostgresqlCluster resource
      name: test-database # Name of the PostgreSQL database
      owner: test-user # Database owner role
    

    The manifest defines only the required fields, such as the cluster name, database name, and owner role.

    Configuration with the libc locale provider and the locale, localeCollate, and localeCType parameters.

    apiVersion: postgresql.stackland.yandex.cloud/v1alpha1
    kind: PostgresqlDatabase
    metadata:
      name: test-cluster-test-database
    spec:
      cluster: test-cluster
      name: test-database
      owner: test-user
      template: template1 # Template for the database
      encoding: UTF8 # Character encoding
      localeProvider: libc # Locale provider
      locale: en_US.UTF-8 # Default locale
      localeCollate: en_US.UTF-8 # String sorting rule
      localeCType: en_US.UTF-8 # Character classification rule
    

    Configuration with the icu locale provider and the icuLocale and icuRules parameters. Available in PostgreSQL and later.

    apiVersion: postgresql.stackland.yandex.cloud/v1alpha1
    kind: PostgresqlDatabase
    metadata:
      name: test-cluster-test-database
    spec:
      cluster: test-cluster
      name: test-database
      owner: test-user
      template: template1
      encoding: UTF8
      localeProvider: icu # Locale provider
      icuLocale: en-US # ICU locale name
      icuRules: "" # Additional ICU collation rules
    

    Configuration with the builtin locale provider and the builtinLocale parameter. Available in PostgreSQL and later.

    apiVersion: postgresql.stackland.yandex.cloud/v1alpha1
    kind: PostgresqlDatabase
    metadata:
      name: test-cluster-test-database
    spec:
      cluster: test-cluster
      name: test-database
      owner: test-user
      template: template1
      encoding: UTF8
      localeProvider: builtin # locale provider; available in PostgreSQL 17 and later
      builtinLocale: C.UTF-8 # built-in locale name
    

    Configuration with managed PostgreSQL schemas.

    apiVersion: postgresql.stackland.yandex.cloud/v1alpha1
    kind: PostgresqlDatabase
    metadata:
      name: test-cluster-test-database
    spec:
      cluster: test-cluster
      name: test-database
      owner: test-user
      allowConnections: true # Enabling connections to the database
      connectionLimit: -1 # Connection limit; -1 for no limit
      isTemplate: false # Using the database as a template
      tablespace: pg_default # Default tablespace
      schemas: # Managed schemas
        - name: test-schema
          owner: test-user
          state: present # present to create or support; absent to delete
    

    In the spec.schemas section, describe the database schemas by specifying the name, owner (optional), and state (present to create or absent to delete).

  3. Apply the manifest: kubectl apply -f postgresqldatabase.yaml -n <project_name>. Optionally, you can specify the project name in the metadata.namespace resource property and skip it in the command.

Once the database is created, you cannot change the name, template, encoding, localeProvider, locale, localeCollate, localeCType, icuLocale, icuRules, builtinLocale, or collationVersion field.

Was the article helpful?

Previous
Deleting a user
Next
Update database
© 2026 Direct Cursus Technology L.L.C.