I was a bit afraid of query speed but it is almost the same query plan - just extended filter on build_by_pkg_id index scan. Nevertheless, execution time grows ~10x. Random package (10ms vs 94ms) It seems acceptable as it is not called too often.

It's not an idea solution, but I guess it's the best we can do until we get a better solution for associating tasks with CG builds.

It seems acceptable as it is not called too often.

Specifically, it is called:

• at the start of each buildArch task. A few milliseconds here makes no real difference.
• for each load of a taskinfo and buildinfo pages in the web ui. This is a much shorter timescale than buildArch, but still not an issue to add a few milliseconds.
• Ken's chatbot plugin, as described in #1128. Similarly ok.

It's possible that another outside system could be using this call, but I would expect a similar usage pattern if so.

:thumbsup:

Commit b5ff9d8b fixes this pull-request