Unsupported server parameter after Azure flexible PostgreSQL server upgrade v11 to v13

Johannes Boyne 21

We performed a PostgreSQL version upgrade (v11 -> v13) and cannot change any server parameter via the GUI nor via CLI anymore.

The error is:

(ParameterNotExists) The Parameter [azure.allow_hostname_in_username] is invalid or unsupported in current PG version [13]
Code: ParameterNotExists

But we cannot drop this parameter neither, because there is no CLI call or GUI for this. We already tried to reset the server parameters but it failed with the same error.

Mahesh Kurva 2,835 Reputation points Microsoft Vendor

2025-02-24T15:39:16.0633333+00:00
Hi Johannes Boyne,

Welcome to Microsoft Q&A forum.

As I understand it, you're encountering an issue with an unsupported parameter after upgrading PostgreSQL from version 11 to version 13.

The Parameter [azure.allow_hostname_in_username] is invalid or unsupported in current PG version [13]

The parameter azure.allow_hostname_in_username is not supported in PostgreSQL 13 For more information, please refer the document: https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-server-parameters#customized-options

Here’s how you can remove the azure.allow_hostname_in_username parameter before upgrading your PostgreSQL version:

1.Azure Portal:

Navigate to your PostgreSQL server in the Azure Portal.

Go to the Server Parameters section.

Look for the azure.allow_hostname_in_username parameter and set it to its default value or remove it if possible.

2.Azure CLI:

Use the Azure CLI to reset the parameter.

az postgres flexible-server parameter set --resource-group <ResourceGroupName> --server-name <ServerName> --name azure.allow_hostname_in_username --value off

For more information, please refer the document: https://learn.microsoft.com/en-us/cli/azure/postgres/flexible-server/parameter?view=azure-cli-latest#az-postgres-flexible-server-parameter-set

I hope this information helps. Please do let us know if you have any further queries.
Johannes Boyne 21 Reputation points

2025-02-24T16:51:46.31+00:00

I am encountering the issue with an unsupported parameter after upgrading PostgreSQL from version 11 to version 13. Thus, your solution does not work. The parameter is not visible in the UI anymore and also just setting it via CLI leads to the error from above.
Johannes Boyne 21 Reputation points

2025-02-25T07:00:55.77+00:00

Hi Oury,

I understand that. But it does not make sense to fail any changes to server parameters. It puts the server in a broken state. One would assume that resetting the server parameters to default would remove the unsupported parameter.

Let me ask differently, what would be the best next step to not loose the server?
Oury Ba-MSFT 20,351 Reputation points Microsoft Employee

2025-02-25T18:26:16.4233333+00:00

Johannes Boyne

Could you please define what do you mean by "put the server in a broken state"?
Johannes Boyne 21 Reputation points

2025-02-25T20:43:30.97+00:00
@Oury Ba-MSFT

We performed a PostgreSQL version upgrade (v11 -> v13)

The DB is now v13

We have to change a server parameter either via GUI or via CLI but it is not possible due to the error:

(ParameterNotExists) The Parameter [azure.allow_hostname_in_username] is invalid or unsupported in current PG version

So from our understanding it is not possible to change any server parameter anymore in the current state if the validation is failing due to azure.allow_hostname_in_username
Oury Ba-MSFT 20,351 Reputation points Microsoft Employee

2025-02-27T18:08:41.1233333+00:00

@Johannes Boyne It should not cause failure to change any server parameters.

Please give me sometimes to try this from my end and get back with proper results and findings.

Thank you for your patience while we check on this.

Regards,

Oury
Oury Ba-MSFT 20,351 Reputation points Microsoft Employee

2025-02-27T18:24:08.4033333+00:00

@Johannes Boyne Please check Private message.
Oury Ba-MSFT 20,351 Reputation points Microsoft Employee

2025-02-27T20:06:39.49+00:00

@Johannes Boyne Could you please a screen shot of your server parameters page.

Regards,

Oury

1 answer

Oury Ba-MSFT 20,351 Reputation points Microsoft Employee

2025-02-24T23:15:39.24+00:00

@Johannes Boyne Thank you for reaching out.

This GUC was added to the azure extension only for version 11 of Postgres, because it was required for migration scenarios from Single Server to Flexible Server. Once the server is migrated to Flex, you can upgrade to higher versions, but that GUC isn't available, because it isn't necessary outside of the specific context of migration from PGSS 11 to PGFS 11.

As shared by Mahesh above. It is not supported on higher version of Azure PostgreSQL flex.

Regards,

Oury
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Unsupported server parameter after Azure flexible PostgreSQL server upgrade v11 to v13

1 answer

Your answer