Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com Path: not-for-mail From: Dan Holmsand Subject: Re: please try the latest snapshot Date: Fri, 17 Jan 2003 17:34:38 +0100 Lines: 29 Message-ID: References: <20030117055216.GA4969@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030115 X-Accept-Language: en-us, en In-Reply-To: Dan Holmsand wrote: > Indeed it does seem to stop the BSODding on my machines. Thanks! Still no BSOD. However, now I'm having trouble with postgresql: the postmaster dies as soon as I exit psql. Reverting to a cygwin1.dll built from cvs from four days ago fixes the problem. Here is what the postmaster.log says: LOG: server process (pid 1440) was terminated by signal 11 LOG: terminating any other active server processes LOG: all server processes terminated; reinitializing shared memory and semaphores IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not enough core 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 1441792 bytes), reduce PostgreSQL's shared_buffers parameter (currently 64) and/or its max_connections parameter (currently 32). The PostgreSQL Administrator's Guide contains more information about shared memory configuration. /dan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/