Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

table public.cache_invalidation_stream is growing #3643

Closed
sivadmp opened this issue Aug 2, 2018 · 2 comments
Closed

table public.cache_invalidation_stream is growing #3643

sivadmp opened this issue Aug 2, 2018 · 2 comments

Comments

@sivadmp
Copy link

sivadmp commented Aug 2, 2018

hi
the sizes of the following tables are very large
I can truncate them

 public.received_transactions                             | 2302 MB
 public.cache_invalidation_stream                         | 2270 MB
 public.event_json                                        | 1608 MB
 public.events                                            | 786 MB
 public.event_auth                                        | 754 MB
 public.event_edges                                       | 568 MB
 public.device_inbox                                      | 527 MB
 public.state_groups_state                                | 512 MB
 public.event_search                                      | 365 MB
 public.event_push_actions                                | 326 MB
 public.event_reference_hashes                            | 311 MB
 public.event_to_state_groups                             | 178 MB
 public.stream_ordering_to_exterm                         | 173 MB
@richvdh
Copy link
Member

richvdh commented Aug 8, 2018

For cache_invalidation_stream, see #3665.

For received_transactions, try:

select to_timestamp(ts/1000), * from received_transactions order by ts limit 1;

It should be within the last month. If so, then the automated clearout is working correctly and there isn't much else to be done.

@richvdh
Copy link
Member

richvdh commented Aug 21, 2018

closing pending further information

@richvdh richvdh closed this as completed Aug 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants