Configure server parameters in Azure Database for PostgreSQL - Flexible Server via the Azure portal
APPLIES TO: 
Azure Database for PostgreSQL - Flexible Server
You can list, show, and update configuration parameters for an Azure Database for PostgreSQL flexible server instance through the Azure portal. In addition, you can also click on the Server Parameter Tabs to easily view parameter group as Modified, Static, Dynamic and Read-Only.
Prerequisites
To step through this how-to guide you need:
Viewing and editing parameters
Open the Azure portal.
Select your Azure Database for PostgreSQL flexible server instance.
Under the SETTINGS section, select Server parameters. The page shows a list of parameters, their values, and descriptions.
Select the drop down button to see the possible values for enumerated-type parameters like client_min_messages.
Select or hover over the i (information) button to see the range of possible values for numeric parameters like cpu_index_tuple_cost.
If needed, use the search box to narrow down to a specific parameter. The search is on the name and description of the parameters.
Change the parameter values you would like to adjust. All changes you make in a session are highlighted in purple. Once you have changed the values, you can select Save. Or you can Discard your changes.
List all the parameters that are modified from their default value.
If you have saved new values for the parameters, you can always revert everything back to the default values by selecting Reset all to default.
Working with time zone parameters
If you plan to work with date and time data in PostgreSQL, you'll want to ensure that you've set the correct time zone for your location. All timezone-aware dates and times are stored internally in PostgreSQL in UTC. They are converted to local time in the zone specified by the TimeZone server parameter before being displayed to the client. This parameter can be edited on Server parameters page as explained above. PostgreSQL allows you to specify time zones in three different forms:
A full time zone name, for example Asia/Shanghai. The recognized time zone names are listed in the pg_timezone_names view.
Example to query this view in psql and get list of time zone names:select name FROM pg_timezone_names LIMIT 20;
You should see result set like:
name ----------------------- GMT0 Iceland Factory NZ-CHAT America/Panama America/Fort_Nelson America/Pangnirtung America/Belem America/Coral_Harbour America/Guayaquil America/Marigot America/Barbados America/Porto_Velho America/Bogota America/Menominee America/Martinique America/Asuncion America/Toronto America/Tortola America/Managua (20 rows)A time zone abbreviation, for example PST. Such a specification merely defines a particular offset from UTC, in contrast to full time zone names which can imply a set of daylight savings transition-date rules as well. The recognized abbreviations are listed in the pg_timezone_abbrevs view Example to query this view in psql and get list of time zone abbreviations:
select abbrev from pg_timezone_abbrevs limit 20;
You should see result set like:
abbrev| ------+ ACDT | ACSST | ACST | ACT | ACWST | ADT | AEDT | AESST | AEST | AFT | AKDT | AKST | ALMST | ALMT | AMST | AMT | ANAST | ANAT | ARST | ART |In addition to the timezone names and abbreviations, PostgreSQL will accept POSIX-style time zone specifications of the form STDoffset or STDoffsetDST, where STD is a zone abbreviation, offset is a numeric offset in hours west from UTC, and DST is an optional daylight-savings zone abbreviation, assumed to stand for one hour ahead of the given offset.
Next steps
Learn about: