TonyS <tony@xxxxxxxxxxxxxxxxxxx> writes: > The analyze function has crashed again while the overcommit entries were > as above. The last bit of the PostgreSQL log shows: > MdSmgr: 41934848 total in 14 blocks; 639936 free (0 chunks); 41294912 used > ident parser context: 0 total in 0 blocks; 0 free (0 chunks); 0 used > hba parser context: 7168 total in 3 blocks; 2288 free (1 chunks); 4880 used > LOCALLOCK hash: 8192 total in 1 blocks; 1680 free (0 chunks); 6512 used > Timezones: 83472 total in 2 blocks; 3744 free (0 chunks); 79728 used > ErrorContext: 8192 total in 1 blocks; 8160 free (6 chunks); 32 used > 2015-04-01 14:23:27 EDT ERROR: out of memory > 2015-04-01 14:23:27 EDT DETAIL: Failed on request of size 80. > 2015-04-01 14:23:27 EDT STATEMENT: analyze verbose; We need to see all of that memory map, not just the last six lines of it. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
