Run ANALYZE after fiddling with stats (#16849)

Introduced in #16833

Fixes #16844
This commit is contained in:
Erik Johnston 2024-01-24 13:57:12 +00:00 committed by GitHub
parent 594842cf7f
commit adf15c4f6b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 19 additions and 0 deletions

1
changelog.d/16849.bugfix Normal file
View File

@ -0,0 +1 @@
Fix database performance regression due to changing Postgres table statistics. Introduced in v1.100.0rc1.

View File

@ -16,3 +16,5 @@
-- figuring that out by itself.
ALTER TABLE event_auth_chain_links ALTER origin_chain_id SET (n_distinct = -0.5);
ALTER TABLE event_auth_chain_links ALTER target_chain_id SET (n_distinct = -0.5);
-- We should have done an `ANALYZE event_auth_chain_links` here, but we forgot.

View File

@ -0,0 +1,16 @@
--
-- This file is licensed under the Affero General Public License (AGPL) version 3.
--
-- Copyright (C) 2023 New Vector, Ltd
--
-- This program is free software: you can redistribute it and/or modify
-- it under the terms of the GNU Affero General Public License as
-- published by the Free Software Foundation, either version 3 of the
-- License, or (at your option) any later version.
--
-- See the GNU Affero General Public License for more details:
-- <https://www.gnu.org/licenses/agpl-3.0.html>.
-- We need to do an ANALYZE after `01_auth_links_stats.sql.postgres`, where we
-- fiddled with the stats.
ANALYZE event_auth_chain_links;