mirror of
https://git.anonymousland.org/anonymousland/synapse.git
synced 2024-09-07 10:41:57 +00:00
Add upgrade notes about disk space for events migration (#10314)
This commit is contained in:
parent
7a5873277e
commit
d7a94a7dcc
@ -1,3 +1,7 @@
|
|||||||
|
Synapse 1.38.0 (**UNRELEASED**)
|
||||||
|
===============================
|
||||||
|
This release includes a database schema update which could result in elevated disk usage. See the [upgrade notes](https://matrix-org.github.io/synapse/develop/upgrade.md#upgrading-to-v1380) for more information.
|
||||||
|
|
||||||
Synapse 1.37.1 (2021-06-30)
|
Synapse 1.37.1 (2021-06-30)
|
||||||
===========================
|
===========================
|
||||||
|
|
||||||
|
1
changelog.d/10314.bugfix
Normal file
1
changelog.d/10314.bugfix
Normal file
@ -0,0 +1 @@
|
|||||||
|
Fix a long-standing bug where Synapse would return errors after 2<sup>31</sup> events were handled by the server.
|
@ -85,6 +85,44 @@ process, for example:
|
|||||||
dpkg -i matrix-synapse-py3_1.3.0+stretch1_amd64.deb
|
dpkg -i matrix-synapse-py3_1.3.0+stretch1_amd64.deb
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
|
# Upgrading to v1.38.0
|
||||||
|
|
||||||
|
## Re-indexing of `events` table on Postgres databases
|
||||||
|
|
||||||
|
This release includes a database schema update which requires re-indexing one of
|
||||||
|
the larger tables in the database, `events`. This could result in increased
|
||||||
|
disk I/O for several hours or days after upgrading while the migration
|
||||||
|
completes. Furthermore, because we have to keep the old indexes until the new
|
||||||
|
indexes are ready, it could result in a significant, temporary, increase in
|
||||||
|
disk space.
|
||||||
|
|
||||||
|
To get a rough idea of the disk space required, check the current size of one
|
||||||
|
of the indexes. For example, from a `psql` shell, run the following sql:
|
||||||
|
|
||||||
|
```sql
|
||||||
|
SELECT pg_size_pretty(pg_relation_size('events_order_room'));
|
||||||
|
```
|
||||||
|
|
||||||
|
We need to rebuild **four** indexes, so you will need to multiply this result
|
||||||
|
by four to give an estimate of the disk space required. For example, on one
|
||||||
|
particular server:
|
||||||
|
|
||||||
|
```
|
||||||
|
synapse=# select pg_size_pretty(pg_relation_size('events_order_room'));
|
||||||
|
pg_size_pretty
|
||||||
|
----------------
|
||||||
|
288 MB
|
||||||
|
(1 row)
|
||||||
|
```
|
||||||
|
|
||||||
|
On this server, it would be wise to ensure that at least 1152MB are free.
|
||||||
|
|
||||||
|
The additional disk space will be freed once the migration completes.
|
||||||
|
|
||||||
|
SQLite databases are unaffected by this change.
|
||||||
|
|
||||||
|
|
||||||
# Upgrading to v1.37.0
|
# Upgrading to v1.37.0
|
||||||
|
|
||||||
## Deprecation of the current spam checker interface
|
## Deprecation of the current spam checker interface
|
||||||
|
Loading…
Reference in New Issue
Block a user