order by cidr_block causes a hang on the query?

[e-gineer]

This works great:

> select vpc_id, cidr_block, region from aws_vpc;
+--------------+---------------+-----------+
| vpc_id       | cidr_block    | region    |
+--------------+---------------+-----------+
| vpc-af92a1d4 | 10.85.0.0/16  | us-east-1 |
| vpc-a7025cc0 | 172.30.0.0/24 | us-east-1 |
| vpc-3cd69054 | 10.84.0.0/16  | us-east-2 |
| vpc-12947a7b | 172.31.0.0/16 | eu-west-2 |
| vpc-87389aef | 10.84.0.0/16  | eu-west-2 |
| vpc-7032c619 | 172.31.0.0/16 | us-east-2 |
| vpc-82fc47e7 | 172.31.0.0/16 | us-east-1 |
| vpc-abb765ce | 172.31.0.0/16 | us-west-2 |
| vpc-0434cd61 | 172.31.0.0/16 | us-west-1 |
| vpc-fb848d9e | 172.31.0.0/16 | eu-west-1 |
| vpc-6f2d5c09 | 10.85.0.0/16  | eu-west-1 |
+--------------+---------------+-----------+

But it hangs once I add the order by?

> select vpc_id, cidr_block, region from aws_vpc order by cidr_block;
⠦ Loading results... 
⠇ Loading results... 
⠹ Loading results... 
⠼ Loading results... 
⠋ Loading results... 
⠹ Loading results... 
⠸ Loading results... 
⠏ Loading results... 

FYI, order by vpc_id does work:

> select vpc_id, cidr_block, region from aws_vpc order by vpc_id;
+--------------+---------------+-----------+
| vpc_id       | cidr_block    | region    |
+--------------+---------------+-----------+
| vpc-0434cd61 | 172.31.0.0/16 | us-west-1 |
| vpc-12947a7b | 172.31.0.0/16 | eu-west-2 |
| vpc-3cd69054 | 10.84.0.0/16  | us-east-2 |
| vpc-6f2d5c09 | 10.85.0.0/16  | eu-west-1 |
| vpc-7032c619 | 172.31.0.0/16 | us-east-2 |
| vpc-82fc47e7 | 172.31.0.0/16 | us-east-1 |
| vpc-87389aef | 10.84.0.0/16  | eu-west-2 |
| vpc-a7025cc0 | 172.30.0.0/24 | us-east-1 |
| vpc-abb765ce | 172.31.0.0/16 | us-west-2 |
| vpc-af92a1d4 | 10.85.0.0/16  | us-east-1 |
| vpc-fb848d9e | 172.31.0.0/16 | eu-west-1 |
+--------------+---------------+-----------+

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 90 days with no activity.