Re: [HACKERS] Spinlock error - Mailing list pgsql-hackers

From Jeff MacDonald
Subject Re: [HACKERS] Spinlock error
Date
Msg-id Pine.BSF.4.10.10001272307060.380-100000@rage.hub.org
Whole thread Raw
In response to Re: [HACKERS] Spinlock error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi Tom,

Thanks for that info, do know if thre is anyway, to
get more information from postmaster or postges ?

i'd really like to be able to solve this, i'll see if i 
can reproduce the condition.



======================================================
Jeff MacDonaldjeff@pgsql.com    irc: bignose on EFnet
======================================================

On Thu, 27 Jan 2000, Tom Lane wrote:

> "Jeff MacDonald <jeff@pgsql.com>" <jeffm@pgsql.com> writes:
> > After those spinlock errors the postmaster died.... I tries to start it
> > back up and it failed with this error.
> 
> You may need to clean up shared memory blocks and/or semaphores ---
> those are supposed to be deallocated when the postmaster quits,
> but it sounds like it didn't happen.  See the pgsql ipcclean script.
> 
> Not sure what caused the stuck spinlock in the first place.
> 
>             regards, tom lane
> 
> ************
> 



pgsql-hackers by date:

Previous
From: Kristofer Munn
Date:
Subject: Backend Core Dumping
Next
From: The Hermit Hacker
Date:
Subject: [6.5.2] potentially major bug?