"Qingqing Zhou" <zhouqq@cs.toronto.edu> wrote
>
>
> ExecutorState: 550339936 total in 123 blocks; 195005920 free (740144
chunks); 355334016 used
> ...
> HashBatchContext: 293593176 total in 44 blocks; 3107384 free (80 chunks);
290485792 used
> TIDBitmap: 2088960 total in 8 blocks; 1012120 free (27 chunks); 1076840
used
> ...
> HashBatchContext: 2080768 total in 7 blocks; 346888 free (11 chunks);
1733880 used
> HashTableContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used
> HashBatchContext: 2080768 total in 7 blocks; 325264 free (11 chunks);
1755504 used
> HashTableContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used
> HashBatchContext: 41877664 total in 11 blocks; 4845648 free (15 chunks);
37032016 used
> TIDBitmap: 2088960 total in 8 blocks; 1012120 free (27 chunks); 1076840
used
>
> [repeated sequenced like this ...]
>
> ERROR: out of memory
> DETAIL: Failed on request of size 344.
> CONTEXT: SQL statement "INSERT INTO "tblSummary" SELECT * FROM
"qrySummary""
> PL/pgSQL function "refresh_matview" line 13 at execute statement
> LOG: autovacuum: processing database "iqdb"
> LOG: autovacuum: processing database "template1"LOG: autovacuum:
processing database "postgres"
Er, looks like a huge hash-join but not sure if it is a memory leak, Tom?
Regards,
Qingqing