X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 25BC69FA30C for ; Mon, 5 Jun 2006 15:41:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 62323-01 for ; Mon, 5 Jun 2006 15:41:16 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by postgresql.org (Postfix) with ESMTP id 4B55D9FA12F for ; Mon, 5 Jun 2006 15:41:16 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id d42so1550146pyd for ; Mon, 05 Jun 2006 11:41:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KiMA3BK+rHWXjMrvQjfGJls3wIKE29mtd+M75THm/b5l0Y+0RQ/dBytardYyb6OOGBtftQIotvw8QwKU2aanowlzs7kxB6qcTlQJUJrQyJTHYZErFcyaBgO6fIomZyAGUgaf5CB6CEAvANVM1tGnkne+ikTDODXA52q1up9HE/s= Received: by 10.35.105.18 with SMTP id h18mr6917318pym; Mon, 05 Jun 2006 11:41:13 -0700 (PDT) Received: by 10.35.22.20 with HTTP; Mon, 5 Jun 2006 11:41:13 -0700 (PDT) Message-ID: Date: Mon, 5 Jun 2006 19:41:13 +0100 From: "Guido Barosio" To: Callis Subject: Re: postgres dying Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/18 X-Sequence-Number: 21980 Hi Callis, It would be great to understand how it is dying. Note that you've just said that it keeps dying, but you haven't explained us "how is it dying". Therefore, are you able to explain us how / when is it dying? Let me know if I am not clear on my request :) Best wishes, Guido. On 6/5/06, Callis wrote: > Hi all, > > Please pardon me if it sound naive or its been answered. > I am running freeradius with postgresql for VOIP with > Cisco gateways. But my server keeps dying and after tuning > the SHMMX and number of connections and all that i still > get the same results. > > Any form of help will be greatly appreciated. > > Thank you. > > System: Fedora 3 > CPU : 3GHZ pentium(IV) > RAM : 2GB > HDD : 3 35GB hardisks > Freeradius: freeradius-1.0.1-1 > Postgresql: postgresql-7.4.6-1.FC3.1 > > Postgresql.conf: > ================ > tcpip_socket = true > max_connections = 180 > # note: increasing max_connections costs about > 500 bytes of shared > # memory per connection slot, in addition to > costs from shared_buffers > # and max_locks_per_transaction. > superuser_reserved_connections = 4 > > > #--------------------------------------------------------------------------- > # RESOURCE USAGE (except WAL) > #--------------------------------------------------------------------------- > > # - Memory - > > #Set to 256MB > shared_buffers = 24000 # min 16, at least > max_connections*2, 8KB each > > sort_mem = 32168 # min 64, size in KB > #vacuum_mem = 8192 # min 1024, size in KB > > # - Free Space Map - > > #max_fsm_pages = 20000 # min > max_fsm_relations*16, 6 bytes each > #max_fsm_relations = 1000 # min 100, ~50 bytes each > > # - Kernel Resource Usage - > > #max_files_per_process = 1000 # min 25 > #preload_libraries = '' > ===================================== END ============ > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > -- Guido Barosio ----------------------- http://www.globant.com guido.barosio@globant.com