Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • 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 Managed Service for PostgreSQL
  • Getting started
  • Access management
  • Pricing policy
  • Terraform reference
    • API authentication
      • Overview
        • Overview
        • ListRunningRepacks
        • LaunchRepack
        • TerminateRepack
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • gRPC request
  • LaunchRepackRequest
  • RepackSpec
  • RepackTarget
  • LaunchRepackResponse
  • FinishedRepack
  • RunningRepack
  • RepackSpec
  • RepackTarget
  1. API reference
  2. gRPC
  3. ManagedRepack
  4. LaunchRepack

Managed Service for PostgreSQL API, gRPC: ManagedRepackService.LaunchRepack

Written by
Yandex Cloud
Updated at July 1, 2026
View in Markdown
  • gRPC request
  • LaunchRepackRequest
  • RepackSpec
  • RepackTarget
  • LaunchRepackResponse
  • FinishedRepack
  • RunningRepack
  • RepackSpec
  • RepackTarget

Launches new Repack in given cluster

gRPC requestgRPC request

rpc LaunchRepack (LaunchRepackRequest) returns (LaunchRepackResponse)

LaunchRepackRequestLaunchRepackRequest

{
  "cluster_id": "string",
  "spec": {
    "type": "RepackType",
    "dbname": "string",
    "targets": [
      {
        "schema": "string",
        // Includes only one of the fields `name`, `all_in_schema`
        "name": "string",
        "all_in_schema": "bool"
        // end of the list of possible fields
      }
    ],
    "wait_timeout": "int64",
    "jobs": "int64"
  },
  "start_timeout": "google.protobuf.Duration",
  "launch_id": "string"
}

Request to launch a new Repack in a cluster.

Field

Description

cluster_id

string

Required field. Required. ID of the PostgreSQL cluster that Repack is running in.
To get the cluster ID use a ClusterService.List request.

The maximum string length in characters is 50.

spec

RepackSpec

Required field. Specification of repack to launch

start_timeout

google.protobuf.Duration

Initial timeout to tell finished immediately from running repacks
Defaults to 1 second, if not specified

launch_id

string

UUID of launch to be set by client

RepackSpecRepackSpec

Represents specification for launching new Repack process

Field

Description

type

enum RepackType

Which objects to repack

  • REPACK_TYPE_INDEX: Repack indexes.
  • REPACK_TYPE_TABLE: Repack tables.

dbname

string

database name this repack process is working with

targets[]

RepackTarget

list of target objects this repack process is working with

wait_timeout

int64

pg_repack option; timeout to cancel other backends on conflict

jobs

int64

pg_repack option; Use this many parallel jobs for each table

RepackTargetRepackTarget

Single object to repack

Field

Description

schema

string

Schema of object to be repacked
If not given, defaults to "public"

name

string

Name of object to be repacked

Includes only one of the fields name, all_in_schema.

Object to repack within the schema.

all_in_schema

bool

All objects within given schema are to be repacked

Includes only one of the fields name, all_in_schema.

Object to repack within the schema.

LaunchRepackResponseLaunchRepackResponse

{
  // Includes only one of the fields `finished`, `running`
  "finished": {
    "cluster_id": "string",
    "exit_code": "int64",
    "launch_id": "string"
  },
  "running": {
    "cluster_id": "string",
    "start_time": "google.protobuf.Timestamp",
    "spec": {
      "type": "RepackType",
      "dbname": "string",
      "targets": [
        {
          "schema": "string",
          // Includes only one of the fields `name`, `all_in_schema`
          "name": "string",
          "all_in_schema": "bool"
          // end of the list of possible fields
        }
      ],
      "wait_timeout": "int64",
      "jobs": "int64"
    },
    "launch_id": "string"
  }
  // end of the list of possible fields
}

Result of a Repack launch.

Field

Description

finished

FinishedRepack

Returned if pg_repack finishes immediately before start_timeout expires

Includes only one of the fields finished, running.

Outcome of the launch: finished immediately or still running.

running

RunningRepack

Returned if pg_repack still runs after start_timeout expires

Includes only one of the fields finished, running.

Outcome of the launch: finished immediately or still running.

FinishedRepackFinishedRepack

Represents already finished repack process

Field

Description

cluster_id

string

Which cluster this repack was launched in

exit_code

int64

Exit code of this repack launch

launch_id

string

UUID of launch, identifier of specific instance of launched repack

RunningRepackRunningRepack

Represents currently running repack process

Field

Description

cluster_id

string

Which cluster this repack runs in

start_time

google.protobuf.Timestamp

When this repack process has been started

spec

RepackSpec

Specification for this running repack

launch_id

string

UUID of launch, identifier of specific instance of launched repack

RepackSpecRepackSpec

Represents specification for launching new Repack process

Field

Description

type

enum RepackType

Which objects to repack

  • REPACK_TYPE_INDEX: Repack indexes.
  • REPACK_TYPE_TABLE: Repack tables.

dbname

string

database name this repack process is working with

targets[]

RepackTarget

list of target objects this repack process is working with

wait_timeout

int64

pg_repack option; timeout to cancel other backends on conflict

jobs

int64

pg_repack option; Use this many parallel jobs for each table

RepackTargetRepackTarget

Single object to repack

Field

Description

schema

string

Schema of object to be repacked
If not given, defaults to "public"

name

string

Name of object to be repacked

Includes only one of the fields name, all_in_schema.

Object to repack within the schema.

all_in_schema

bool

All objects within given schema are to be repacked

Includes only one of the fields name, all_in_schema.

Object to repack within the schema.

Was the article helpful?

Previous
ListRunningRepacks
Next
TerminateRepack
© 2026 Direct Cursus Technology L.L.C.