# Transaction Wraparound Report(Postgres) Transaction wraparound is a significant challenge in PostgreSQL, and this new feature is designed to help analyze and predict it. For a given database, it provides the percentage progress toward wraparound and identifies potential issues such as idle transactions, inactive replication slots, and other factors that may be hindering the freezing process Demo video **HTML Report (Sample)**

**Identifying the problem database** Once you identify that this issue is occurring, you'll likely want to know which database is responsible. The table below in the report highlights the top 5 databases contributing to the problem

**Transactions Per Seconds Vs Time to hit wraparound point (Reference table)** The reference table below provides an estimate of the time required to exhaust 2 billion transactions. **Note:** Calculate your transactions per second (TPS) during peak workload periods and compare it with the table. Additionally, identify any factors that might be hindering freezing activity

**Wraparound Stats** Below report helps you identify potential issues like idle transactions, inactive replication slots, and other factors that could be slowing down the freezing process

--- # Agent Instructions: 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: ``` GET https://klouddb.gitbook.io/klouddb_shield/transaction-wraparound-report-postgres.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.