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 …

No. The only thing we discovered is that when removing the record from the requests table in PostgreSQL, the requests part still appears in the session. Here we only use the session replay part of the tool, so perhaps that’s why we didn’t notice any difference.

Thanks for the reply. We’re having the opposite but similar issue of clickhouse growing weekly by 10gb, but postgres staying quite flat growing at maybe 100mb. I want to purge sessions to see if that clears out the old clickhouse stored data, but am not sure anymore where the front-door for purgin…

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

Questions & Answers

mccrackend March 23, 2026, 2:02pm 2

Have you learned anything more about this topic and how it relates to the clickhouse database?

Topic		Replies	Views
Clickhouse cleanup query Questions & Answers storage	1	29	March 23, 2026
Sessions not loading Issues & Bugs session-replay	0	74	February 25, 2025
Technical events aren't shown in session replay Issues & Bugs	1	106	January 6, 2025
Which service sends replays to S3? Questions & Answers storage	1	88	April 16, 2024
How to retain existing session data from VM s mounted disk, into a s3 object storage in GCP, which recently configured to the cluster 📺 Session Replay docker , kubernetes , session-replay , storage	1	47	February 28, 2025

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

Related topics