When required to ensure the health of your instance, we may schedule maintenance operations on your behalf (for example, to modify
instance storage size).
For a detailed description of how instance maintenance is carried out by our platform, see Snowflake Postgres Maintenance.
可用操作
The following operations are available from the Manage dropdown menu on your instance details page in the dashboard:
Fork - Create a new instance from an existing instance
Modify - Change the instance size, storage size, or Postgres version of the instance
You can fork an instance to create a new instance from an existing instance, optionally choosing a point in time to fork from. By default
the new instance will be forked from the current state of the source instance. Read more about forking in Snowflake Postgres point-in-time recovery.
Modifying your instance’s resource configuration or major version requires a failover maintenance. See
Snowflake Postgres maintenance failover for more information.
要进行更改,请执行以下操作:
In the navigation menu, select Postgres.
选择您的实例。
In the Manage menu at the top right, select Modify.
Select the new COMPUTE_FAMILY and/or storage size from the dropdown menus. See Postgres major version upgrades for more
information about changing the Postgres version.
Alternatively, you can use an APPLY ON ‘<timestamp>’ clause to specify a future date or timestamp up to three days from the current
for the maintenance failover to proceed.
COMPUTE_FAMILY and STORAGE_SIZE_GB changes made to a primary instance are not also applied to any present read replicas. They require
their own Modify operations.
COMPUTE_FAMILY 和 STORAGE_SIZE_GB 变更 也 适用于 HA 备用,如果为给定实例启用了 HA。对于这些操作,HA 备用实例替换总是在其替换实例准备就绪后立即进行,因为这不需要将其主服务器停机。
Changes to an instance’s Postgres major version work via a Snowflake Postgres maintenance failover
operation just as with other Modify operations, but there are some important differences where HA and read replica instances are concerned.
Postgres 主要版本升级操作只能应用于主实例。当主实例进行主要版本升级时,通过从主实例升级完成 后 创建的全新备份重建这些实例,将相同的升级应用于任何现有的只读副本和 HA 实例。
这意味着在运行主实例升级后的全新备份,并根据该备份构建新的 HA 和/或只读副本实例所需的时间内:
主实例将没有有效的 HA 实例存在。
While they will remain accessible, read replicas will have stale data since they will not replicate from the primary until their
replacement instances are ready.
When High Availability (HA) is enabled, your instance includes a standby host that replaces the primary if your primary
becomes unavailable. You can read more about this in Snowflake Postgres High Availability.
创建副本
You can create a replica of your instance from the dashboard. A replica is a read-only copy of the source instance that is kept in sync
with the source instance. Find about more about creating and using replicas in Snowflake Postgres Read Replicas.
In the Manage menu at the top right, select Resume.
Click the Resume button to confirm the action.
要恢复 Snowflake Postgres 实例,请运行 ALTER POSTGRES INSTANCE … RESUME:
ALTERPOSTGRESINSTANCE[IFEXISTS] <name> RESUME
这些操作是异步的。可使用 DESCRIBE 命令跟踪这些操作的状态。
示例:恢复名为 my_instance 的 Snowflake Postgres 实例
ALTERPOSTGRESINSTANCE my_instance RESUME;
刷新
Refresh is a instance maintenance operation that will replace your instance without making any changes
to its configured resources. Use this to ensure your instance has up-to-date OS security patches, the latest Postgres minor version for its
given major version, and works properly with the latest Snowflake Postgres features.
In the navigation menu, select Postgres.
选择您的实例。
In the Manage menu at the top right, select Refresh.
If you want the Refresh maintenance failover to occur as soon as the replacement server is ready, select
Bypass maintenance Window and apply immediately.
Click the Refresh button to confirm the action.
To run an instance Refresh via SQL use ALTER POSTGRES INSTANCE with the COMPUTE_FAMILY value matching its current value. For
example, if you have a STANDARD_M instance named myinstance use this to run a Refresh maintenance and have the maintenance’s
failover operation happen during the first maintenance window after the replacement server is ready:
Use this to have the Refresh maintenance failover to occur as soon as the replacement server is ready instead of waiting for
its next maintenance window if it has one set:
You can restart either PostgreSQL or the underlying server that runs your Postgres instance if needed. This type of instance management
operation restarts the server in-place, without creating a replica or performing a fail-over. Read more about restarting services in
Snowflake Postgres maintenance restart.
重新生成凭据
Regenerating credentials will return a new connection string for your database instance, replacing the existing credentials. Read more about
this topic in Snowflake Postgres Roles.
自定义配置参数
You can make changes to many of Postgres’s own server settings for your Snowflake Postgres instances. You can see the list of available
configuration parameters in Snowflake Postgres Server Settings.
Changes to some of the Postgres settings may require an instance restart to take effect. These changes will not take effect
unless you specify APPLY IMMEDIATELY in the ALTER POSTGRES INSTANCE statement. For the list of settings that require a restart,
consult the table in Postgres settings.
Any instance management operation, whether it’s creating a new instance or modifying an existing
one, takes some time to complete. The exact duration depends on many factors, including your
data and schema sizes, and how busy your instance is. An instance’s state gives
you insight into the progress of an ongoing operation. It is shown in the dashboard, or you can
check it by running the DESCRIBE POSTGRES INSTANCE command.
Latest base backup is being restored to the server
Variable
Starting
Starting
Postgres is being started on the instance and WAL that accumulated during base backup is being applied
Variable
Replaying
Replaying
Accumulated WAL since last base backup is being replayed
Variable
Finalizing
Finalizing
Instance configuration is being finalized and the server is being made available
1-2 minutes
Ready
Ready
New instance matches source instance and is ready for the operation to proceed. If scheduled for an upcoming maintenance window, the instance is kept Ready until that time. If scheduled for now, the operation proceeds once it reaches Ready. Running instances normally show the Ready state.
N/A
N/A
您可能在平台上看到的其他实例状态:
State
What’s happening
Typical duration
Next state
Restarting
Underlying server is being restarted
1-2 minutes
Ready
Resuming
A new server is being built and a suspended instance is being resumed