Skip site navigation (1) Skip section navigation (2)

Re: Solaris ASM problem

From: Kris Jurka <books(at)ejurka(dot)com>
To: Theo Schlossnagle <jesus(at)omniti(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Solaris ASM problem
Date: 2006-04-28 21:18:49
Message-ID: Pine.BSO.4.63.0604281614560.8518@leary2.csoft.net (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackerspgsql-patches

On Fri, 28 Apr 2006, Theo Schlossnagle wrote:

> The file that uses the spinlocks:
> /src/backend/storage/lmgr/s_lock.c
>
> can be compiled standalone with -DS_LOCK_TEST
>

To get the test to compile I had to link in tas.o as the attached patch 
shows.  Unfortunately this doesn't work for platforms that don't have a 
tas.o, bailing out with file not found.  Perhaps it's not important to fix 
this test, but I thought I'd mention it.

Anyway the test exits with

Stuck spinlock (80618e9) detected at ./s_lock.c:355.

on a linux gcc build this exits with

Stuck spinlock (0x5013ad) detected at ./s_lock.c:402.

Kris Jurka

Attachment: slocktest.patch
Description: text/plain (722 bytes)

In response to

Responses

pgsql-hackers by date

Next:From: Theo SchlossnagleDate: 2006-04-28 21:30:59
Subject: Re: Solaris ASM problem
Previous:From: Alvaro HerreraDate: 2006-04-28 21:09:28
Subject: Re: Logging pg_autovacuum

pgsql-committers by date

Next:From: Theo SchlossnagleDate: 2006-04-28 21:30:59
Subject: Re: Solaris ASM problem
Previous:From: Tom LaneDate: 2006-04-28 20:57:59
Subject: pgsql: Remove the restriction originally coded into

pgsql-patches by date

Next:From: Theo SchlossnagleDate: 2006-04-28 21:30:59
Subject: Re: Solaris ASM problem
Previous:From: Theo SchlossnagleDate: 2006-04-28 20:44:29
Subject: Re: Solaris ASM problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group