> 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/appendixes/datetime-appendix.md).

# Appendix B. Date/Time Support

**Table of Contents**

[B.1. Date/Time Input Interpretation](/appendixes/datetime-appendix/datetime-input-rules.md)

[B.2. Handling of Invalid or Ambiguous Timestamps](/appendixes/datetime-appendix/datetime-invalid-input.md)

[B.3. Date/Time Key Words](/appendixes/datetime-appendix/datetime-keywords.md)

[B.4. Date/Time Configuration Files](/appendixes/datetime-appendix/datetime-config-files.md)

[B.5. POSIX Time Zone Specifications](/appendixes/datetime-appendix/datetime-posix-timezone-specs.md)

[B.6. History of Units](/appendixes/datetime-appendix/datetime-units-history.md)

[B.7. Julian Dates](/appendixes/datetime-appendix/datetime-julian-dates.md)

PostgreSQL uses an internal heuristic parser for all date/time input support. Dates and times are input as strings, and are broken up into distinct fields with a preliminary determination of what kind of information can be in the field. Each field is interpreted and either assigned a numeric value, ignored, or rejected. The parser contains internal lookup tables for all textual fields, including months, days of the week, and time zones.

This appendix includes information on the content of these lookup tables and describes the steps used by the parser to decode dates and times.

***

原文：[PostgreSQL 18.6 Documentation](https://www.postgresql.org/docs/18/datetime-appendix.html)（英文原文，待翻譯）


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.postgresql.tw/appendixes/datetime-appendix.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.