@User interesting... I wonder if there is a way we can hint or force Postgres to not do that (if it is indeed the issue)