Queries are 2x faster, but we're making some event properties temporary
Blog post from PostHog
PostHog plans to overhaul event storage on November 30, 2026, aiming to reduce duplication, preserve native property types, and speed queries by about 35% on average, with larger gains for event-property filtering and session-based analysis. Raw person-update instructions such as $set and $set_once, along with specified SDK, replay, transport, and feature-flag diagnostic properties, will remain available for 60 days after event receipt before being deleted, while the resulting person properties will continue to be stored and queryable normally. Feature-flag evaluation events will move to a dedicated table with 90-day retention, and individual $feature/<flag> properties will become a feature-flags map without disrupting existing insights or HogQL queries. PostHog will also stop storing several deprecated properties, including flag payloads, surveys and product-tour fields, internal SDK state, transformation diagnostics, and raw AI payloads, the latter of which already reside in a dedicated AI observability table with 30-day retention.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Observability | 3 | 3,071 | 738 | 185 | +11% |
| LLM | 2 | 6,548 | 1,236 | 233 | +8% |
| Data Pipeline | 1 | 401 | 160 | 72 | +47% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.