X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D033DD1B187 for ; Fri, 11 Jun 2004 18:19:02 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 33145-02 for ; Fri, 11 Jun 2004 21:19:03 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id BD1E0D1B1CB for ; Fri, 11 Jun 2004 18:19:00 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i5BLJ0DW052067 for ; Fri, 11 Jun 2004 21:19:00 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i5BKuNNn048715 for pgsql-admin@postgresql.org; Fri, 11 Jun 2004 20:56:23 GMT From: "Michael Fork" X-Newsgroups: comp.databases.postgresql.admin Subject: FreeBSD SHMMAX Date: Fri, 11 Jun 2004 16:56:28 -0400 Organization: Hub.Org Networking Services Lines: 44 Message-ID: X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=2.2 tagged_above=0.0 required=5.0 tests=FORGED_YAHOO_RCVD, FROM_ENDS_IN_NUMS, PRIORITY_NO_NAME X-Spam-Level: ** X-Archive-Number: 200406/156 X-Sequence-Number: 13816 All, I am trying to get Postgres running on FreeBSD and am running into problems with shared mem. Here is the postgres error messge: FATAL: could not create shared memory segment: Cannot allocate memory DETAIL: Failed system call was shgmet(key=5432001, size=103407616, 03600). HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space. To reduce the request size (currently 103407616 bytes), reduce PostgreSQL's shared_buffers parameter (currently 12288) and/or its max_connections parameter (cureently 40). The PostgreSQL documentation contains more information about shared memory configuration. Here is the output of sysctl (which shows there is more shared mem available than postgres is asking for): bash-2.05b$ sysctl -a | grep shm kern.ipc.shmmax: 200000000 kern.ipc.shmmin: 1 kern.ipc.shmmni: 192 kern.ipc.shmseg: 128 kern.ipc.shmall: 8192 kern.ipc.shm_use_phys: 0 and finally the IPC stats which shows nothing being used: Message Queues: T ID KEY MODE OWNER GROUP Shared Memory: T ID KEY MODE OWNER GROUP Semaphores: T ID KEY MODE OWNER GROUP Any ideas why postgres won't start? Thanks. Michael