Re: Out of memory error when doing an update with IN clause - Mailing list pgsql-general (2024)

Home>mailing lists

Tom,I run this:explain update f_commerce_impressions set servlet_key = 60 whereservlet_key in (68,69,70,71,87,90,94,91,98,105,106);ERROR: out of memoryDETAIL: Failed on request of size 1024.I get this in the server log:TopMemoryContext: 32768 total in 3 blocks; 6376 free (4 chunks); 26392 usedTopTransactionContext: 8192 total in 1 blocks; 8136 free (0 chunks); 56 usedDeferredTriggerXact: 0 total in 0 blocks; 0 free (0 chunks); 0 usedMessageContext: 57344 total in 3 blocks; 28760 free (1 chunks); 28584 usedPortalMemory: 8192 total in 1 blocks; 8040 free (0 chunks); 152 usedPortalHeapMemory: 8192 total in 1 blocks; 3936 free (0 chunks); 4256 usedPortalHeapMemory: 23552 total in 5 blocks; 2888 free (0 chunks); 20664 usedExecutorState: 24576 total in 2 blocks; 5032 free (8 chunks); 19544 usedDynaHashTable: 534773784 total in 65 blocks; 31488 free (255 chunks);534742296 usedExprContext: 0 total in 0 blocks; 0 free (0 chunks); 0 usedCacheMemoryContext: 516096 total in 6 blocks; 205344 free (1 chunks);310752 usedidx_commerce_impressions_servlet: 1024 total in 1 blocks; 640 free (0chunks); 384 usedidx_commerce_impressions_page_view: 1024 total in 1 blocks; 640 free (0chunks); 384 usedidx_commerce_impressions_date_dec_2003: 1024 total in 1 blocks; 640 free(0 chunks); 384 usedidx_commerce_impressions_date_nov_2003: 1024 total in 1 blocks; 640 free(0 chunks); 384 usedf_commerce_impressions_pkey: 1024 total in 1 blocks; 640 free (0chunks); 384 usedpg_index_indrelid_index: 1024 total in 1 blocks; 640 free (0 chunks);384 usedpg_attrdef_adrelid_adnum_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_amop_opc_strategy_index: 1024 total in 1 blocks; 320 free (0 chunks);704 usedpg_shadow_usename_index: 1024 total in 1 blocks; 640 free (0 chunks);384 usedpg_amop_opr_opc_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 usedpg_conversion_oid_index: 1024 total in 1 blocks; 640 free (0 chunks);384 usedpg_language_name_index: 1024 total in 1 blocks; 640 free (0 chunks); 384usedpg_statistic_relid_att_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_attribute_relid_attnam_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_shadow_usesysid_index: 1024 total in 1 blocks; 640 free (0 chunks);384 usedpg_cast_source_target_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_conversion_name_nsp_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_trigger_tgrelid_tgname_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_namespace_nspname_index: 1024 total in 1 blocks; 640 free (0 chunks);384 usedpg_conversion_default_index: 2048 total in 1 blocks; 704 free (0chunks); 1344 usedpg_class_relname_nsp_index: 1024 total in 1 blocks; 320 free (0 chunks);704 usedpg_aggregate_fnoid_index: 1024 total in 1 blocks; 640 free (0 chunks);384 usedpg_inherits_relid_seqno_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_language_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 usedpg_type_typname_nsp_index: 1024 total in 1 blocks; 320 free (0 chunks);704 usedpg_group_sysid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 usedpg_namespace_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384usedpg_proc_proname_args_nsp_index: 2048 total in 1 blocks; 704 free (0chunks); 1344 usedpg_opclass_am_name_nsp_index: 2048 total in 1 blocks; 768 free (0chunks); 1280 usedpg_group_name_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 usedpg_proc_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 usedpg_operator_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 usedpg_amproc_opc_procnum_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_index_indexrelid_index: 1024 total in 1 blocks; 640 free (0 chunks);384 usedpg_operator_oprname_l_r_n_index: 2048 total in 1 blocks; 704 free (0chunks); 1344 usedpg_opclass_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 usedpg_rewrite_rel_rulename_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_type_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 usedpg_attribute_relid_attnum_index: 1024 total in 1 blocks; 320 free (0chunks); 704 usedpg_class_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 usedMdSmgr: 8192 total in 1 blocks; 6120 free (0 chunks); 2072 usedDynaHash: 8192 total in 1 blocks; 7064 free (0 chunks); 1128 usedDynaHashTable: 8192 total in 1 blocks; 5080 free (0 chunks); 3112 usedDynaHashTable: 8192 total in 1 blocks; 2008 free (0 chunks); 6184 usedDynaHashTable: 8192 total in 1 blocks; 3016 free (0 chunks); 5176 usedDynaHashTable: 8192 total in 1 blocks; 4040 free (0 chunks); 4152 usedDynaHashTable: 24576 total in 2 blocks; 13240 free (4 chunks); 11336 usedDynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 usedDynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 usedDynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 usedDynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 usedDynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 usedErrorContext: 8192 total in 1 blocks; 8176 free (0 chunks); 16 usedERROR: out of memoryDETAIL: Failed on request of size 1024.Tom Lane wrote:>Sean Shanny <shannyconsulting@earthlink.net> writes:>>>>As you can see I had to reduce the number of arguments in the IN clause>>to even get the explain.>>>>>>You mean you get an out-of-memory error just from EXPLAIN (without>ANALYZE)?? That makes even less sense ... the hash table we identified>before should not be created or filled during EXPLAIN.>> regards, tom lane>>---------------------------(end of broadcast)--------------------------->TIP 9: the planner will ignore your desire to choose an index scan if your> joining column's datatypes do not match>>>