Notices by Stefan Marr (smarr@mastodon.acm.org)

@freemo the full schema is here:

https://github.com/smarr/ReBenchDB/blob/2414426bb93a9c170004a97207593217f02f622b/src%2Fbackend%2Fdb%2Fdb.sql#L152

@freemo 1) yes. there's an index. And the explain shows it's used with the index scan.

2) The group by is needed to get the iteration data together from which the array is created.

The long story is given here: https://stackoverflow.com/q/78130781/916546 with examples how the data looks like.

I ended up with a PostgreSQL query that takes 1.5h to transform a data set of 6GB.🤨

Feels like an eternity. 🤔
https://gist.github.com/smarr/5a30c34cc38e274f634b151d9763f93c

https://mastodon.acm.org/@smarr/112062771665024203

@freemo hm, I would assume there's an index on the primary key:
https://github.com/smarr/ReBenchDB/blob/2414426bb93a9c170004a97207593217f02f622b/src/backend/db/db.sql#L152

Would you have a suggestion what other indexes might be helpful here? Thanks.

@freemo @freemo@qoto.org

The concrete query is in the Gist here: https://gist.github.com/smarr/5a30c34cc38e274f634b151d9763f93c

On the partial table, an index on (runId, trialId, criterion, invocation) helps. Though, since this converts the full table, adding that index doesn't make any performance difference for the full conversion.

I added a comment on the Gist with the `EXPLAIN ANALYZE` output. It's the first time doing performance work on this type of stuff, so, many unknowns on my end....