pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
could not fork new process for connection: Cannot allocate memory 4+ messages / 4 participants [nested] [flat]
* could not fork new process for connection: Cannot allocate memory @ 2004-07-20 13:41 Pavel Veretennikov <vermut@kid.lv> 2004-07-25 23:07 ` Re: could not fork new process for connection: Cannot allocate memory Gaetano Mendola <mendola@bigfoot.com> 0 siblings, 1 reply; 4+ messages in thread From: Pavel Veretennikov @ 2004-07-20 13:41 UTC (permalink / raw) To: pgsql-admin I ran into this error running 2 user connection executing consecutive selects in a loop. What could be a problem? About 3G of shared memory is allocated to PG, 850000 shared_buffers. TopMemoryContext: 32768 total in 3 blocks; 20024 free (22 chunks); 12744 used TopTransactionContext: 8192 total in 1 blocks; 8136 free (0 chunks); 56 used DeferredTriggerXact: 0 total in 0 blocks; 0 free (0 chunks); 0 used MessageContext: 253952 total in 5 blocks; 87568 free (3 chunks); 166384 used PortalMemory: 8192 total in 1 blocks; 8040 free (0 chunks); 152 used PortalHeapMemory: 1024 total in 1 blocks; 936 free (0 chunks); 88 used ExecutorState: 24576 total in 2 blocks; 40 free (1 chunks); 24536 used ExprContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used ExprContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used ExprContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used ExprContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used ExprContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used ExprContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used ExprContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used CacheMemoryContext: 1040384 total in 7 blocks; 496440 free (1 chunks); 543944 used gs_finance_requests_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_dic_currency_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_players_ipaccesse_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_players_statuses_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_dic_cities_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_players_login_alert_pkey: 1024 total in 1 blocks; 320 free (0 chunks); 704 used gs_players_grps_members_pkey: 1024 total in 1 blocks; 320 free (0 chunks); 704 used gs_players_accounts_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_dic_banks_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_players_grps_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_dic_countries_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_players_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_constraint_conrelid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_rooms_childrooms_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used gs_rooms_pkey: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_index_indrelid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_attrdef_adrelid_adnum_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_amop_opc_strategy_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_shadow_usename_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_amop_opr_opc_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_conversion_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_language_name_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_statistic_relid_att_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_attribute_relid_attnam_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_shadow_usesysid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_cast_source_target_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_conversion_name_nsp_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_trigger_tgrelid_tgname_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_namespace_nspname_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_conversion_default_index: 2048 total in 1 blocks; 704 free (0 chunks); 1344 used pg_class_relname_nsp_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_aggregate_fnoid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_inherits_relid_seqno_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_language_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_type_typname_nsp_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_group_sysid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_namespace_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_proc_proname_args_nsp_index: 2048 total in 1 blocks; 704 free (0 chunks); 1344 used pg_opclass_am_name_nsp_index: 2048 total in 1 blocks; 768 free (0 chunks); 1280 used pg_group_name_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_proc_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_operator_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_amproc_opc_procnum_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_index_indexrelid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_operator_oprname_l_r_n_index: 2048 total in 1 blocks; 704 free (0 chunks); 1344 used pg_opclass_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_rewrite_rel_rulename_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_type_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used pg_attribute_relid_attnum_index: 1024 total in 1 blocks; 320 free (0 chunks); 704 used pg_class_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used MdSmgr: 8192 total in 1 blocks; 6120 free (0 chunks); 2072 used DynaHash: 8192 total in 1 blocks; 7064 free (0 chunks); 1128 used DynaHashTable: 8192 total in 1 blocks; 5080 free (0 chunks); 3112 used DynaHashTable: 8192 total in 1 blocks; 2008 free (0 chunks); 6184 used DynaHashTable: 8192 total in 1 blocks; 1984 free (0 chunks); 6208 used DynaHashTable: 8192 total in 1 blocks; 3520 free (0 chunks); 4672 used DynaHashTable: 24576 total in 2 blocks; 13240 free (4 chunks); 11336 used DynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 used DynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 used DynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 used DynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 used DynaHashTable: 0 total in 0 blocks; 0 free (0 chunks); 0 used ErrorContext: 8192 total in 1 blocks; 8176 free (3 chunks); 16 used ERROR: out of memory DETAIL: Failed on request of size 104. LOG: could not fork new process for connection: Cannot allocate memory ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: could not fork new process for connection: Cannot allocate memory 2004-07-20 13:41 could not fork new process for connection: Cannot allocate memory Pavel Veretennikov <vermut@kid.lv> @ 2004-07-25 23:07 ` Gaetano Mendola <mendola@bigfoot.com> 2004-07-26 05:24 ` Re: could not fork new process for connection: Cannot allocate memory Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 4+ messages in thread From: Gaetano Mendola @ 2004-07-25 23:07 UTC (permalink / raw) To: Pavel Veretennikov <vermut@kid.lv>; +Cc: pgsql-admin -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pavel Veretennikov wrote: | What could be a problem? About 3G of shared memory is allocated to PG, | 850000 shared_buffers. I don't know what you problem can be but are you sure you need that *very huge* ammount of shared memory ? Let us know your tipical usage of your system. I seen many Postgres installation with bunch of SHM wasted !!! Regards Gaetano Mendola -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBBD0x7UpzwH2SGd4RAiGqAKDai6Pyu/rsN3zMhMtAj964U9PfMgCeIYX3 3YFXWB++pl55PMZmMQIHZEU= =CA0p -----END PGP SIGNATURE----- ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: could not fork new process for connection: Cannot allocate memory 2004-07-20 13:41 could not fork new process for connection: Cannot allocate memory Pavel Veretennikov <vermut@kid.lv> 2004-07-25 23:07 ` Re: could not fork new process for connection: Cannot allocate memory Gaetano Mendola <mendola@bigfoot.com> @ 2004-07-26 05:24 ` Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 4+ messages in thread From: Tom Lane @ 2004-07-26 05:24 UTC (permalink / raw) To: Gaetano Mendola <mendola@bigfoot.com>; +Cc: Pavel Veretennikov <vermut@kid.lv>; pgsql-admin Gaetano Mendola <mendola@bigfoot.com> writes: > Pavel Veretennikov wrote: > | What could be a problem? About 3G of shared memory is allocated to PG, > | 850000 shared_buffers. > I don't know what you problem can be but are you sure you need that > *very huge* ammount of shared memory ? Conventional wisdom is that setting shared_buffers higher than a few tens of thousands is a bad idea, no matter how much RAM you have. See the pgsql-performance archives. regards, tom lane ^ permalink raw reply [nested|flat] 4+ messages in thread
* could not fork new process for connection: Cannot allocate memory @ 2006-10-24 04:48 Mr. Dan <bitsandbytes88@hotmail.com> 0 siblings, 0 replies; 4+ messages in thread From: Mr. Dan @ 2006-10-24 04:48 UTC (permalink / raw) To: pgsql-admin Hi, We are running v814 with 8 GB of RAM and 3.5 GB allocated to shared memory. It's never been a problem for us before. We ran into a situation yesterday where we received the message above. At that time our total available memory took a dive to 4GB and cached memory stayed around 4 GB. Soon after that some process ended and everything returned to normal. It alsted around 10 minutes. Too bad I didn't see the query or process at the time it was running. ~DjK _________________________________________________________________ Try the next generation of search with Windows Live Search today! http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&source=hmtagline ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2006-10-24 04:48 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2004-07-20 13:41 could not fork new process for connection: Cannot allocate memory Pavel Veretennikov <vermut@kid.lv> 2004-07-25 23:07 ` Gaetano Mendola <mendola@bigfoot.com> 2004-07-26 05:24 ` Tom Lane <tgl@sss.pgh.pa.us> 2006-10-24 04:48 could not fork new process for connection: Cannot allocate memory Mr. Dan <bitsandbytes88@hotmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox