> ## Documentation Index
> Fetch the complete documentation index at: https://private-7c7dfe99-trino-dialect.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings

> Configure PostgreSQL and PgBouncer parameters and manage instance settings for ClickHouse Managed Postgres

export const Image = ({img, alt, size = "lg", background}) => {
  const normalizedSize = ["sm", "md", "lg"].includes(size) ? size : "lg";
  const backgroundColor = background === "white" ? "white" : background === "black" ? "rgb(31 31 28)" : undefined;
  return <div className={`ch-image-${normalizedSize}`}>
      <Frame>
        <img src={img} alt={alt} style={{
    backgroundColor
  }} />
      </Frame>
    </div>;
};

export const BetaBadge = ({link, galaxyTrack, galaxyEvent}) => {
  if (link) {
    return <a href={link} target="_blank" rel="noopener noreferrer" className="betaBadge" onClick={galaxyTrack && galaxyEvent ? galaxyOnClick(galaxyEvent) : undefined}>
                <span>Beta</span>
            </a>;
  }
  return <a href="https://clickhouse.com/docs/reference/settings/beta-and-experimental-features#beta-features" className="betaBadge">
            <span>Beta feature</span>
        </a>;
};

<BetaBadge link="https://clickhouse.com/cloud/postgres" galaxyTrack={true} galaxyEvent="docs.managed-postgres.settings-beta" />

You can modify configuration parameters and manage instance settings for your ClickHouse Managed Postgres instance through the **Settings** tab in the sidebar.

<h2 id="service-actions">
  Service actions and scaling
</h2>

<Image img="https://mintcdn.com/private-7c7dfe99-trino-dialect/xUD5t8rQeJvNiIFp/images/managed-postgres/service-actions.webp?fit=max&auto=format&n=xUD5t8rQeJvNiIFp&q=85&s=68b4b3fd715e28db0efd2bfc0474d2ea" alt="Service actions and scaling" size="md" border width="1708" height="756" data-path="images/managed-postgres/service-actions.webp" />

The **Service actions** toolbar provides controls for managing your ClickHouse Managed Postgres instance:

* **Reset password**: Update the superuser password (only when the instance is `Running`)
* **Restart**: Restart the database instance (only when the instance is `Running`)
* **Delete**: Delete the instance

The **Scaling** section allows you to change the instance types of your primary and standbys to increase or decrease computing resources and storage capacity.
See [scaling page](/products/managed-postgres/scaling) for more details.

<h2 id="changing-configuration">
  Changing configuration parameters
</h2>

<Image img="https://mintcdn.com/private-7c7dfe99-trino-dialect/xUD5t8rQeJvNiIFp/images/managed-postgres/postgres-parameters.webp?fit=max&auto=format&n=xUD5t8rQeJvNiIFp&q=85&s=25be0278ff082190c90700faf2ef59ae" alt="Postgres parameters configuration" size="md" border width="2508" height="1498" data-path="images/managed-postgres/postgres-parameters.webp" />

To modify a parameter, select the **Edit parameters** button. Select the parameters you need to modify and change their values accordingly. Once you're satisfied with your changes, press the **Save Changes** button.

All changes made to the configuration parameters are typically persisted to the instance within one minute. Some parameters require a database restart to take effect. These changes will be applied after the next restart, which you can trigger manually from the **Service actions** toolbar.

Refer to the official [documentation](https://www.postgresql.org/docs/current/runtime-config.html) on the configuration parameters. The list of parameters available to set will be extended soon. In the meantime, contact [support](https://clickhouse.com/support/program) to request a parameter not currently supported.

<h2 id="scheduled-upgrades">
  Scheduled upgrades
</h2>

The **Configuration** section also lets you control when platform maintenance — minor PostgreSQL version upgrades, managed service feature updates, and operating system patches — is applied to your instance. Select **Configure schedule** in the **Scheduled upgrades** subsection to pick a two-hour UTC window and, optionally, the days of the week on which upgrades may be applied.

For the available windows and what a schedule does and doesn't cover, see [scheduled upgrades](/products/managed-postgres/upgrades#scheduled-upgrades).