tencent cloud

Data Transfer Service

Physical Migration Inspection Items

Baixar
Modo Foco
Tamanho da Fonte
Última atualização: 2026-10-16 20:15:25
Traduzido por IA
The items to check before a physical migration task is initiated for TencentDB for PostgreSQL are detailed below:

Database Connection Check

For details, causes, and remediation methods of the specific checks, see Connect to DB Check.

Version Check

The major versions of the source and target instances must be consistent, and the kernel version of the target instance must not be lower than the following version.
Major Version
Kernel Version
10
v10.17_r1.5
11
v11.12_r1.5
12
v12.7_r1.5
13
v13.3_r1.4
14
v14.2_r1.11
15
v15.1_r1.4
16
v16.0_r1.2

Source Instance Permission Check

Checking Details

The migration account for the source instance must have the LOGIN and REPLICATION permissions.
The configuration of the pg_hba.conf file on the source instance must meet the system requirements.

Fixing Method

Grant the user the corresponding permissions as required in the check requirement, and then execute the verification task again.
The statement to grant the LOGIN permission to account XXXX is `alter user XXXX LOGIN;`. The statement to grant the REPLICATION permission to the account is `alter user XXXX REPLICATION;`.
Additionally, if a migration task reports an error similar to connect source with replication failed: pq: no pg_hba.conf entry for replication connection from host "xx.xx.xxx.xx", user "xxx", it indicates that the configuration of the pg_hba.conf file on the source instance does not meet the migration requirements. To resolve this, add the configuration host replication all 0.0.0.0/0 md5 to the pg_hba.conf file on the source instance, and then either restart the instance or execute select pg_reload_conf(); to reload the configuration.
Note:
When permission and password conflicts exist between the database accounts of the source and target instances, the system uses the source instance account configuration by default.
If the source instance is a PostgreSQL instance from another cloud provider, use an account with the REPLICATION permission. Otherwise, the migration task will fail the check.

Target Instance Table Existence Check

Checking Details

Check whether the target instance is empty.
Note:
The target instance can have database accounts created by users, but it must not contain any pre-existing databases or objects.

Fixing Method

Delete any existing databases or objects on the target instance.

Initial User Check

Checking Details

An alarm will be triggered for database objects under the user with uid = 10 on the source instance.

Fixing Method

Change the owner of the database objects under the user with uid = 10 to another customer.

Target Instance Space Check

Checking Details

The disk space of the target instance must be greater than 110% of the used disk space of the source instance. Otherwise, an error will be reported.

Fixing Method

Scale out the disk space on the target end. For details, see Adjusting Instance Configuration.

Instance Key Parameter Check

Checking Details

The wal_level of the source instance must be changed to replica or logical.
The block_size of the source and target instances must be the same.
For PostgreSQL instances of versions earlier than 13, the wal_keep_segments parameter of the source instance must be greater than or equal to 256.
For PostgreSQL instances of version 13 and above, the value of the wal_keep_size/wal_segment_size parameter on the source instance must be greater than or equal to 256.
The wal_block_size of the source and target instances must be the same.
The segment_size of the source and target instances must be the same.
The max_connections of the target instance must be greater than or equal to that of the source instance.
The max_wal_senders of the target instance must be greater than or equal to that of the source end.
The max_worker_processes of the target instance must be greater than or equal to that of the source end.

Fixing Method

Modify the parameters of the source or target instance accordingly based on the requirements specified in the check details.

Plugin Conflict Check

Checking Details

The system checks whether the plugins installed on the source instance are in the list of plugins supported by the target instance. If they are not, the system reports an error. Additionally, if the plugin versions on the source instance are inconsistent with those on the target instance, the system issues a warning.

Fixing Method

Ensure the plugins on the source and target instances are consistent by installing or upgrading the plugins.

Parameter Conflict Check

Checking Details

In principle, the parameter values of the source and target instances should be consistent. When the system detects an inconsistency between the source and target end parameter values, the typical handling method is to use the parameter values of the target instance and not notify the user. The parameters with different handling methods are as follows:
Parameter Name
Default Migration Handling
Validation Action
data_checksums
Use the source instance parameter value.
No alert when parameter values are inconsistent.
enable_partitionwise_aggregate
Use the source instance parameter value.
No alert when parameter values are inconsistent.
enable_partitionwise_join
Use the source instance parameter value.
No alert when parameter values are inconsistent.
lc_ctype
Use the source instance parameter value.
No alert when parameter values are inconsistent.
max_locks_per_transaction
Use the source instance parameter value.
No alert when parameter values are inconsistent.
max_prepared_transactions
Use the source instance parameter value.
No alert when parameter values are inconsistent.
random_page_cost
Use the source instance parameter value.
No alert when parameter values are inconsistent.
max_connections
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
max_wal_senders
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
max_worker_processes
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
array_nulls
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
authentication_timeout
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_analyze_scale_factor
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_analyze_threshold
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_freeze_max_age
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_multixact_freeze_max_age
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_naptime
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_vacuum_cost_delay
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_vacuum_cost_limit
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_vacuum_insert_scale_factor
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_vacuum_insert_threshold
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_vacuum_scale_factor
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
autovacuum_vacuum_threshold
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
bytea_output
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
check_function_bodies
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
constraint_exclusion
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
cursor_tuple_fraction
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
DateStyle
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
deadlock_timeout
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
default_statistics_target
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
default_transaction_isolation
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
exit_on_error
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
extra_float_digits
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
from_collapse_limit
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
geqo
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
geqo_effort
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
geqo_generations
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
geqo_pool_size
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
geqo_seed
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
geqo_selection_bias
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
geqo_threshold
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
idle_in_transaction_session_timeout
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
idle_session_timeout
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
IntervalStyle
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
jit
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
jit_above_cost
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
jit_inline_above_cost
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
jit_optimize_above_cost
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
join_collapse_limit
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
lc_monetary
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
lc_numeric
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
lc_time
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
local_preload_libraries
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
log_filename
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
max_logical_replication_workers
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
max_parallel_workers
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
max_replication_slots
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
max_standby_archive_delay
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
max_standby_streaming_delay
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
recursive_worktable_factor
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
search_path
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
statement_timeout
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
stats_fetch_consistency
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
TimeZone
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
vacuum_cost_delay
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
vacuum_cost_limit
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
vacuum_cost_page_dirty
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
vacuum_cost_page_hit
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
vacuum_cost_page_miss
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
vacuum_freeze_min_age
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
vacuum_freeze_table_age
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
vacuum_multixact_freeze_min_age
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
vacuum_multixact_freeze_table_age
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.
wal_level
Use the target instance parameter value.
Alert the user to modify when parameter values are inconsistent. If not modified, adopt the default migration handling method.

Fixing Method

Modify the parameter values according to your actual needs.

Target Instance Status Check

Checking Details

TDE data encryption cannot be enabled on the target instance.
The target instance can have a read-only group but cannot have associated read-only instances.
User connections are currently not allowed on the target instance.
Note:
When physical migration is performed, ensure that the source instance is not an encrypted instance.

Fixing Method

TDE instances and read-only instances are currently not supported.

GLIBC Version Compatibility Check

Checking Details

Check for GLIBC version compatibility issues between the source and target instances.
Note:
In GLIBC version 2.28, the collation rules for some UTF8 characters have been changed. When versions are incompatible, the data collation rules differ, which poses a risk of unexpected sorting results.

Fixing Method

Upgrade the GLIBC version.

Ajuda e Suporte

Esta página foi útil?

comentários