action #112850
openopenQA Project - coordination #128366: [epic] further improvement after we did ensure all our database tables accomodate enough data
Make pgstatstatements persistent on OSD (in salt)
0%
Description
Motivation¶
In #112718 we have enabled https://www.postgresql.org/docs/current/pgstatstatements.html but it's not yet made persistent. We should make sure it is.
Updated by okurz over 2 years ago
- Copied from coordination #112718: [alert][osd] openqa.suse.de is not reachable anymore, response times > 30s, multiple alerts over the weekend added
Updated by nicksinger about 2 years ago
- Status changed from New to Feedback
- Assignee set to nicksinger
https://progress.opensuse.org/issues/112850 as a first draft. Need to get some feedback from @mkittler (https://suse.slack.com/archives/C02AJ1E568M/p1658223896087059) what was actually changed. The following lines might need to be included in this MR:
# Debugging for https://progress.opensuse.org/issues/112718
compute_query_id = on
pg_stat_statements.max = 10000
pg_stat_statements.track = all
Updated by nicksinger about 2 years ago
- Status changed from Feedback to New
- Assignee deleted (
nicksinger)
Clarified, additional lines have been added. Further discussion needs to happen if we enable this feature by default all the time or just have it in the config (see discussion in https://suse.slack.com/archives/C02AJ1E568M/p1658223896087059). Putting back into new due to this
Updated by okurz 12 months ago
- Related to action #130594: Upgrade osd webUI host to openSUSE Leap 15.5 added
Updated by okurz 12 months ago
I ran into an issue on OSD webUI upgrade to Leap15.5. The postgres service failed to start with
could not access file "pg_stat_statements": No such file or directory
eventually when a salt CI pipeline triggered changes that caused the postgresql service to restart. That happened after in the above mentioned upgrade I called zypper rm -u postgresql$oldver postgresql$oldver-contrib postgresql$oldver-server which due to the -u parameter also removed postgresql-contrib which in turn removed postgresql$newver-contrib which would provide pg_stat_statements but we don't pull that in as hard requirement. Also see https://stackoverflow.com/questions/53158500/postgresql-fatal-could-not-access-file-pg-stat-statements-no-such-file-or-di about this. For now I have the configuration disabled in the config file. If we want to continue here we must ensure we have the contrib package installed as well.