From: | "Jeff MacDonald <jeff(at)pgsql(dot)com>" <jeffm(at)pgsql(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jeff MacDonald <jeff(at)pgsql(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Spinlock error |
Date: | 2000-01-28 03:07:59 |
Message-ID: | Pine.BSF.4.10.10001272307060.380-100000@rage.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 MacDonald
jeff(at)pgsql(dot)com irc: bignose on EFnet
======================================================
On Thu, 27 Jan 2000, Tom Lane wrote:
> "Jeff MacDonald <jeff(at)pgsql(dot)com>" <jeffm(at)pgsql(dot)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
>
> ************
>
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-01-28 03:28:43 | [6.5.2] potentially major bug? |
Previous Message | Kristofer Munn | 2000-01-28 02:28:05 | Backend Core Dumping |