Timeline for Slow query on primary server runs fast on hot standby
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2020 at 22:23 | history | edited | CommunityBot |
added [query-performance] to 2412 questions - Shog9 (Id=1924)
|
|
| Jul 20, 2016 at 18:50 | vote | accept | sudokai | ||
| Jul 18, 2016 at 20:14 | answer | added | jjanes | timeline score: 3 | |
| Jul 18, 2016 at 14:33 | history | tweeted | twitter.com/StackDBAs/status/755047759565250561 | ||
| Jul 18, 2016 at 14:31 | comment | added | Vérace | Hmmm... interesting. Your primary doesn't appear to be under great stress. Can you swap your Primary postgresql.conf out for your mirror's one and see if that helps? I know your server has been up for more than a year and you probably don't want to be rebooting it every time you want to change a parameter. And you also have to consider your entire workload. However, I know from Oracle that it's possible to set the shared pool to too large a value causing response times to increase. Maybe some analagous phenomenon is happening here? | |
| Jul 18, 2016 at 13:36 | history | edited | sudokai | CC BY-SA 3.0 |
added 10849 characters in body
|
| Jul 18, 2016 at 13:29 | history | edited | sudokai | CC BY-SA 3.0 |
added 10849 characters in body
|
| Jul 18, 2016 at 8:06 | review | First posts | |||
| Jul 18, 2016 at 8:07 | |||||
| Jul 18, 2016 at 8:02 | history | asked | sudokai | CC BY-SA 3.0 |