> For the complete documentation index, see [llms.txt](https://docs.postgresql.tw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.postgresql.tw/16/internals/54.-system-views/pg_timezone_abbrevs.md).

# 54.31. pg\_timezone\_abbrevs

The view `pg_timezone_abbrevs` provides a list of time zone abbreviations that are currently recognized by the datetime input routines. The contents of this view change when the [timezone\_abbreviations](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-TIMEZONE-ABBREVIATIONS) run-time parameter is modified.

#### **Table 54.31. `pg_timezone_abbrevs` Columns**

| <p>Column Type</p><p>Description</p>                                                                           |
| -------------------------------------------------------------------------------------------------------------- |
| <p><code>abbrev</code> <code>text</code></p><p>Time zone abbreviation</p>                                      |
| <p><code>utc\_offset</code> <code>interval</code></p><p>Offset from UTC (positive means east of Greenwich)</p> |
| <p><code>is\_dst</code> <code>bool</code></p><p>True if this is a daylight-savings abbreviation</p>            |

While most timezone abbreviations represent fixed offsets from UTC, there are some that have historically varied in value (see [Section B.4](https://www.postgresql.org/docs/current/datetime-config-files.html) for more information). In such cases this view presents their current meaning.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.postgresql.tw/16/internals/54.-system-views/pg_timezone_abbrevs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.