LQO 0.7.0 no longer needs a log or a SQL file. lqo advise --stats reads the workload from pg_stat_statements, which most managed PostgreSQL servers already run. The view stores $1 where the values were, so LQO samples rows from the table each parameter is compared with and builds texts from both common and rare values. All of it is read-only and rolled back.
On the demo, the main trap got the same hint from the view as from the SQL file. On the Join Order Benchmark, the view gave 27 suggestions against 46 from the file. Timed on the benchmark’s own hand-picked values, 12 of those 27 hints also saved 20% or more, 7 changed little and 8 were slower, so hints proven from the view should be checked against real traffic. The release post has the details.