Skip Navigation

[Resolved] wp-views wpv-cache char long generated select disctinct

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 1 reply, has 2 voices.

Last updated by Minesh 1 year, 2 months ago.

Assisted by: Minesh.

Author
Posts
#2641607

I am trying to: Access the homepage and rarely got a bad gateway.

Link to a page where the issue can be seen: hidden link

I expected to see:

Instead, I got:
KILLED QUERY (18104 characters long generated in /nas/content/live/caomultiprod/wp-content/plugins/wp-views/embedded/inc/classes/wpv-cache.class.php:284): #012#011#011#011SELECT DISTINCT t.term_id, tr.object_id#012#011#011#011FROM wp_60_terms AS t INNER JOIN wp_60_term_taxonomy AS tt ON t.term_id = tt.term_id INNER JOIN wp_60_term_relationships AS tr ON tr.term_taxonomy_id = tt.term_taxonomy_id#012#011#011#011WHERE tt.taxonomy IN ('colour-match', 'application', 'feature', 'collection', 'look') AND tr.object_id IN (44907, 44909, 44911, 44913, 44915, 44917, 44919, 44921, 44923, 44925, 44927, 44929, 44931, 44933, 44935, 44937, 44939, 44941, 44943, 44945, 44947, 44949, 44951, 44953, 44955, 44957, 44959, 44961, 44963, 44965, 44967, 44969, 44971, 44973, 44975, 44977, 44979, 44981, 44983, 44985, 44987, 44989, 44991, 44993, 44995, 44997, 44999, 45001, 45003, 45005, 45007, 44855, 44857, 44859, 44861, 44863, 44865, 44867, 40027, 39331, 39332, 39334, 39336, 39861,

#2642055

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

It seems the issue is from server side as you must have large content with your site and that kills the query.

What if you try to use the solution shared with the following links:
- https://stackoverflow.com/questions/23732147/configuring-nginx-for-large-uris
- https://stackoverflow.com/questions/1067334/how-to-set-the-allowed-url-length-for-a-nginx-request-error-code-414-uri-too

Here are few related tickets that might help you:
- https://toolset.com/de/forums/topic/view-generating-killed-query-error/
- https://toolset.com/forums/topic/wp-views-draining-resources/

Does that helps?

You can also get in touch with your server authority and check with them and show them this error and they might help you in this regard as well to configure the server setting accordingly.