Title: Heavy update query for wp_options key wordpress-https_path_cache causes high SQL transaction log growth · Issue #64 · mvied/wordpress-https · GitHub
Open Graph Title: Heavy update query for wp_options key wordpress-https_path_cache causes high SQL transaction log growth · Issue #64 · mvied/wordpress-https
X Title: Heavy update query for wp_options key wordpress-https_path_cache causes high SQL transaction log growth · Issue #64 · mvied/wordpress-https
Description: Hi, I have a very active WP running WordPress 4.9.4 with WordPress HTTPS 3.4.0. Yesterday we started seeing the MySQL transaction log on our server grow rapidly due to a number of extremely heavy update queries to the wp_options table (q...
Open Graph Description: Hi, I have a very active WP running WordPress 4.9.4 with WordPress HTTPS 3.4.0. Yesterday we started seeing the MySQL transaction log on our server grow rapidly due to a number of extremely heavy u...
X Description: Hi, I have a very active WP running WordPress 4.9.4 with WordPress HTTPS 3.4.0. Yesterday we started seeing the MySQL transaction log on our server grow rapidly due to a number of extremely heavy u...
Opengraph URL: https://github.com/mvied/wordpress-https/issues/64
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Heavy update query for wp_options key wordpress-https_path_cache causes high SQL transaction log growth","articleBody":"Hi,\r\n\r\nI have a very active WP running WordPress 4.9.4 with WordPress HTTPS 3.4.0. Yesterday we started seeing the MySQL transaction log on our server grow rapidly due to a number of extremely heavy update queries to the wp_options table (queries in excess of 3 million characters). We did not notice any increase in hit count or change in pattern to the hit count.\r\n\r\nHere is an example of the query (highly truncated because of extreme length).\r\n\r\n`UPDATE wp_options SET option_value = a:63889:{s:19:\\\"/category/featured/\\\";i:0\r\n{truncated}\r\nWHERE option_key = 'wordpress-https_path_cache'`\r\n\r\nIt looks like this might be caused by the update in lib/WordPressHTTPS.php:install():\r\n\r\n`$this-\u003esetSetting('path_cache', $this-\u003e_settings['path_cache'], $blog_id);`\r\n\r\nI can clear the cache from the admin panel, but the size of the database entry continues to grow drastically. \r\n\r\nI am looking to determine exactly what this function is doing, and why it seems to be causing such heavy update queries. I have disabled the plugin until I am able to find out more information\r\n\r\nThanks,\r\nJory\r\n\r\n\r\n","author":{"url":"https://github.com/jormaster3k","@type":"Person","name":"jormaster3k"},"datePublished":"2018-03-08T16:12:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/64/wordpress-https/issues/64"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:470de408-e23d-cfeb-e578-3b9316f71e91 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | BE9E:1A5E8A:1A2CB49:2137E29:69918F16 |
| html-safe-nonce | 9ec7591706227a77ed9774d83119d11bf0918c467960127d20b0af9e014af280 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCRTlFOjFBNUU4QToxQTJDQjQ5OjIxMzdFMjk6Njk5MThGMTYiLCJ2aXNpdG9yX2lkIjoiNjE4MTYwMzY3MDQ4NTk5NTI4NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 0ed6abd8c949533a31e7b9ede0ff22b97ec36114908bc8f66acc78b36974eaf1 |
| hovercard-subject-tag | issue:303537188 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/mvied/wordpress-https/64/issue_layout |
| twitter:image | https://opengraph.githubassets.com/4cd7931c7061e8c2b31bd9076df91c6d839d5e573d117176cbb9b6e0eab279f1/mvied/wordpress-https/issues/64 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/4cd7931c7061e8c2b31bd9076df91c6d839d5e573d117176cbb9b6e0eab279f1/mvied/wordpress-https/issues/64 |
| og:image:alt | Hi, I have a very active WP running WordPress 4.9.4 with WordPress HTTPS 3.4.0. Yesterday we started seeing the MySQL transaction log on our server grow rapidly due to a number of extremely heavy u... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | jormaster3k |
| hostname | github.com |
| expected-hostname | github.com |
| None | 42c603b9d642c4a9065a51770f75e5e27132fef0e858607f5c9cb7e422831a7b |
| turbo-cache-control | no-preview |
| go-import | github.com/mvied/wordpress-https git https://github.com/mvied/wordpress-https.git |
| octolytics-dimension-user_id | 61333573 |
| octolytics-dimension-user_login | mvied |
| octolytics-dimension-repository_id | 2985070 |
| octolytics-dimension-repository_nwo | mvied/wordpress-https |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 2985070 |
| octolytics-dimension-repository_network_root_nwo | mvied/wordpress-https |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 848bc6032dcc93a9a7301dcc3f379a72ba13b96e |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width