Amazon Redshift will no longer support the creation of new Python UDFs starting Patch 198. Existing Python UDFs will continue to function until June 30, 2026. For more information, see the [ blog post ](https://amazonaws-china.com/blogs/big-data/amazon-redshift-python-user-defined-functions-will-reach-end-of-support-after-june-30-2026/).
# Amazon Redshift parameter groups
In Amazon Redshift, you associate a parameter group with each cluster that you create. A *parameter group* is a group of parameters that apply to all of the databases that you create in the cluster. These parameters configure database settings such as query timeout and date style. When you launch a cluster, you must associate it with a parameter group. If you want to change the parameter group later, you can modify the cluster and choose a different parameter group.
Each parameter group has several parameters to configure settings for the database. The list of available parameters depends on the parameter group family to which the parameter group belongs. The default parameter group family is `redshift-2.0`.
Amazon Redshift provides one default parameter group for each parameter group family. The default parameter group has preset values for each of its parameters, and it cannot be modified. The format of the default parameter group name is `default.parameter_group_family`. For example, the default parameter group for the `redshift-2.0` parameter group family is `default.redshift-2.0`.
If you want to use different parameter values than the default parameter group, you must create a custom parameter group and then associate your cluster with it. Initially, the parameter values in a custom parameter group are the same as in the default parameter group. The initial `source` for all of the parameters is `engine-default` because the values are preset by Amazon Redshift. After you change a parameter value, the `source` changes to `user` to indicate that the value has been modified from its default value.
**Note**
The Amazon Redshift console does not display the `source` of each parameter. You must use the Amazon Redshift API, the Amazon CLI, or one of the Amazon SDKs to view the `source`.
For parameter groups that you create, you can modify a parameter value at any time, or you can reset all parameter values to their defaults. You can also associate a different parameter group with a cluster. In some cases, you might modify parameter values in a parameter group that is already associated with a cluster or associate a different parameter group with a cluster. In these cases, you might need to restart the cluster for the updated parameter values to take effect. If the cluster fails and is restarted by Amazon Redshift, your changes are applied at that time. Changes aren't applied if your cluster is restarted during maintenance. For more information, see [WLM dynamic and static properties](workload-mgmt-config.md#wlm-dynamic-and-static-properties).
## Default parameter values
**Note**
As of January 10, 2025, the default value for the `require_ssl` parameter is true. If you don’t want your cluster to require SSL, you can use a custom parameter group when creating the cluster, or modify the cluster to associate it with a custom parameter group after creating the cluster with the default.
The following table shows the default parameter values at a glance with links to more in-depth information about each parameter. These are the default values for the `redshift-2.0` parameter group family.
| Parameter name | Value | More information |
| --- | --- | --- |
| auto\$1analyze | true | [auto\$1analyze](https://docs.amazonaws.cn/redshift/latest/dg/t_Analyzing_tables.html#t_Analyzing_tables-auto-analyze) in the Amazon Redshift Database Developer Guide |
| auto\$1mv | true | [Automated materialized views](https://docs.amazonaws.cn/redshift/latest/dg/materialized-view-auto-mv.html) in the Amazon Redshift Database Developer Guide |
| datestyle | ISO, MDY | [datestyle](https://docs.amazonaws.cn/redshift/latest/dg/r_datestyle.html) in the Amazon Redshift Database Developer Guide |
| enable\$1case\$1sensitive\$1identifier | false | [enable\$1case\$1sensitive\$1identifier](https://docs.amazonaws.cn/redshift/latest/dg/r_enable_case_sensitive_identifier.html) in the Amazon Redshift Database Developer Guide |
| enable\$1user\$1activity\$1logging | false | [Database audit logging](db-auditing.md) in this guide |
| extra\$1float\$1digits | 0 | [extra\$1float\$1digits](https://docs.amazonaws.cn/redshift/latest/dg/r_extra_float_digits.html) in the Amazon Redshift Database Developer Guide |
| max\$1concurrency\$1scaling\$1clusters | 1 | [max\$1concurrency\$1scaling\$1clusters](https://docs.amazonaws.cn/redshift/latest/dg/r_max_concurrency_scaling_clusters.html) in the Amazon Redshift Database Developer Guide |
| query\$1group | default | [query\$1group](https://docs.amazonaws.cn/redshift/latest/dg/r_query_group.html) in the Amazon Redshift Database Developer Guide |
| require\$1ssl | true | [Configuring security options for connections](connecting-ssl-support.md) in this guide |
| search\$1path | \$1user, public | [search\$1path](https://docs.amazonaws.cn/redshift/latest/dg/r_search_path.html) in the Amazon Redshift Database Developer Guide |
| statement\$1timeout | 0 | [statement\$1timeout](https://docs.amazonaws.cn/redshift/latest/dg/r_statement_timeout.html) in the Amazon Redshift Database Developer Guide |
| wlm\$1json\$1configuration | [\$1"auto\$1wlm":true\$1] | [Workload management](workload-mgmt-config.md) in this guide |
| use\$1fips\$1ssl | false | Enable FIPS-compliant SSL mode only if your system is required to be FIPS-compliant. |
**Note**
The `max_cursor_result_set_size` parameter is deprecated. For more information about cursor result set size, see [ Cursor constraints](https://docs.amazonaws.cn/redshift/latest/dg/declare.html#declare-constraints) in the *Amazon Redshift Database Developer Guide*.
You can temporarily override a parameter by using the `SET` command in the database. The `SET` command overrides the parameter for the duration of your current session only. In addition to the parameters listed in the preceding table, you can also temporarily adjust the slot count by setting `wlm_query_slot_count` in the database. The `wlm_query_slot_count` parameter is not available for configuration in parameter groups. For more information about adjusting the slot count, see [wlm\$1query\$1slot\$1count](https://docs.amazonaws.cn/redshift/latest/dg/r_wlm_query_slot_count.html) in the *Amazon Redshift Database Developer Guide*. For more information about temporarily overriding the other parameters, see [ Modifying the server configuration](https://docs.amazonaws.cn/redshift/latest/dg/t_Modifying_the_default_settings.html) in the *Amazon Redshift Database Developer Guide*.