This message was deleted.
# aws
s
This message was deleted.
s
what are the params in
ClusterParameterGroup
? I would guess it's still referncing the old DB version
r
Other than the family (I updated that
14
from
13
, I don't see anything version specific.. unless you mean one of the parameters is no longer supported?
Copy code
ClusterParameterGroup(
        parameter_group_name,
        name=parameter_group_name,
	family="aurora-postgresql14",
        parameters=[
            ClusterParameterGroupParameterArgs(
                name="rds.logical_replication",...
            ),
            ClusterParameterGroupParameterArgs(
                name="rds.force_ssl",...
            ),
            ClusterParameterGroupParameterArgs(
                name="log_min_duration_statement",...
            ),
            ClusterParameterGroupParameterArgs(
                name="shared_preload_libraries",...
            ),
            ClusterParameterGroupParameterArgs(
                name="log_destination",...
            ),
            ClusterParameterGroupParameterArgs(
                name="log_filename",...
            ),
            ClusterParameterGroupParameterArgs(
                name="log_hostname",...
            ),
            ClusterParameterGroupParameterArgs(
                name="log_rotation_age",...
            ),
            ClusterParameterGroupParameterArgs(
                name="log_statement",...
            ),
            ClusterParameterGroupParameterArgs(
                name="rds.log_retention_period",...
            ),
            ClusterParameterGroupParameterArgs(
                name="max_parallel_workers",...
            ),
            ClusterParameterGroupParameterArgs(
                name="max_parallel_workers_per_gather",...
            ),
            ClusterParameterGroupParameterArgs(
                name="max_parallel_maintenance_workers",...
            ),
        ],
    )
s
No, I did mean the family. Hmm i am not sure what's causing the issue then. Is it possible for you to work around this by changing the current parameter group to the default one before attempting the upgrade? Or do you really depend on some of the custom params you set
There's this issue related to cloudformation but I'm wondering if you are also seeing the same issue here: https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1373
r
tomorrow I'll try the steps in the issue 1373 link provided