Clarification about requests table usage in PostgreSQL vs ClickHouse (self-hosted setup)

Questions & Answers
1

Hi everyone,

We’re running a self-hosted OpenReplay setup and noticed that there is a requests table present in both PostgreSQL and ClickHouse.

The issue we’re facing is that the requests table in PostgreSQL keeps growing very quickly, which raises some storage concerns.

To better understand its role, we ran a small test:

  • We generated a new session,

  • Then manually deleted all data from the requests table in PostgreSQL,

  • After that, we were still able to view the full session, including network requests, in the OpenReplay interface.

This suggests that the session data might be read from ClickHouse rather than PostgreSQL.
However, before we make any decision to clear or truncate this table, we’d like to confirm if it’s safe to do so — or if any features depend on the data stored in the PostgreSQL version of the requests table.

Could someone from the team clarify the purpose of this table in PostgreSQL, and whether it’s safe to periodically clean or truncate it?

Thanks in advance for your help!

— Farllon Costa / Aarin