tbe

I had a look at the PR, and i think this issue may result from offset and limit clauses, most likely paired with an order by somewhere in the generated...

> ORDER BY subpath("comment"."path", $10, $11) O dear, sorry i have to say that, but that is bad. Really bad. There is no index that would help here. The database...

OK, i had a look at the query mentioned by @RocketDerp . The column is of type ltree, so there is no issues with substring parsing or things like that....

The more i think about this queries, the more my brain hurts. I will open a new issue to track this kind of problems.

Can you provide me with the contents of `pg_stats` and pg_stat_user_tables ? I struggle to reproduce these seq scans with generated data. Having the stats for database where this issue...

Hi @keithf4 , creating new indexes on huge partition sets is a pain in the a**. And error prone. In a production env, days may pass between creating the index...