-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PostgreSQL - DROP posthog_event
table
#8539
Comments
Can I pick this up? |
Took a few PRs but the PRs:
We still have the model in codebase (as it's referenced via some other tables) and haven't dropped the actual table. I think this is good enough for now and we can TRUNCATE this in production. I'd avoid adding a migration to drop/truncate to avoid potential pain with postgres-users accidentally updating at some future date. |
Nice work 👏 Let's keep this issue open till we actually drop the table. |
This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the |
This issue was closed due to lack of activity. Feel free to reopen if it's still relevant. |
Is your feature request related to a problem?
As we don't host events into PostgreSQL anymore, we should:
Describe the solution you'd like
See above
Describe alternatives you've considered
Do nothing
Additional context
See internal Slack conversation.
The text was updated successfully, but these errors were encountered: