#1963 SQL effectivity for readTaggedBuilds
Closed: Invalid 3 years ago by tkopecek. Opened 4 years ago by tkopecek.

this call is slow and big

SELECT tag.id, tag.name, build.id, build.id, build.version, build.release, build.epoch, build.state, build.completion_time, build.start_time, build.task_id, events.id, events.time, volume.id, volume.name, package.id, package.name, package.name, package.name || '-' || build.version || '-' || build.release, users.id, users.name
            FROM tag_listing, tag, build, users, events, package, volume where
            tag.id = tag_listing.tag_id and
            build.id = tag_listing.build_id and            
            users.id = build.owner and
            events.id = build.create_event and
            package.id = build.pkg_id and
            volume.id = build.volume_id and
            tag_listing.active = TRUE AND tag_id=1234
                AND build.state=1
            ORDER BY tag_listing.create_event DESC;

leads to about 0.8 seconds per call. and 24Mb of tmp file on db server. It could be better.


Metadata Update from @tkopecek:
- Custom field Size adjusted to None
- Issue set to the milestone: 1.24

3 years ago

I can't reproduce it now. Dropping.

Metadata Update from @tkopecek:
- Issue close_status updated to: Invalid
- Issue set to the milestone: None (was: 1.24)
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata