This error was reported when the gp database reported order by

Canceling query because of high VMEM usage. Used: 3659MB, available 819MB, red zone: 7372MB (runaway_cleaner.c:135)
I got this error when I executed a query about a table order by with about 1 billion records, what's good solution?

 

1. Generally: generally split large sql and use intermediate temporary tables

Pull the seq_id field to the temporary table separately, and then select the temporary table

 

2. Set optimizeer to on will not report an error, or adjust VM protect mem