FYI, posting an intermediate update on the issue.
I disabled index scans to keep existing order, and copied part of the
"slow" range into another table (3M rows in 2.2 GB table + 17 GB toast). I
was able to reproduce slow readings from this copy. Then I performed
CLUSTER of the copy using PK and e
Hi,
Does the work mem is used when I do sorts or hash operations on temp
tables ? Or the temp_buffer that is allocated at the beginning of the
session is used for it ?
At one of our apps, the app create a temp table and run on it some
operations (joins,sum,count,avg ) and so on.. I saw in the pos