pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Jakub Ouhrabka <kuba@comgate.cz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Linux/PostgreSQL scalability issue - problem with 8 cores
Date: Mon, 7 Jan 2008 12:12:34 -0300
Message-ID: <20080107151234.GG4723@alvh.no-ip.org> (raw)
In-Reply-To: <4782063C.7070105@comgate.cz>
References: <flii57$748$1@news.hub.org>
	<7083.1199379570@sss.pgh.pa.us>
	<477D1D59.7050002@comgate.cz>
	<4782063C.7070105@comgate.cz>

Jakub Ouhrabka wrote:

> We've tried several times to get stacktrace from some of the running 
> backends during spikes, we got always this:
>
> 0x00002b005d00a9a9 in semop () from /lib/libc.so.6
> #0  0x00002b005d00a9a9 in semop () from /lib/libc.so.6
> #1  0x000000000054fe53 in PGSemaphoreLock (sema=0x2b00a04e5090, 
> interruptOK=0 '\0') at pg_sema.c:411
> #2  0x0000000000575d95 in LWLockAcquire (lockid=SInvalLock, 
> mode=LW_EXCLUSIVE) at lwlock.c:455
> #3  0x000000000056fbfe in ReceiveSharedInvalidMessages 
> (invalFunction=0x5e9a30 <LocalExecuteInvalidationMessage>,
>    resetFunction=0x5e9df0 <InvalidateSystemCaches>) at sinval.c:159
> #4  0x0000000000463505 in StartTransactionCommand () at xact.c:1439
> #5  0x000000000056fa4b in ProcessCatchupEvent () at sinval.c:347
> #6  0x000000000056fb20 in CatchupInterruptHandler 
> (postgres_signal_arg=<value optimized out>) at sinval.c:221
> #7  0x00002b005cf6f110 in killpg () from /lib/libc.so.6
> #8  0x0000000000000000 in ?? ()

Perhaps it would make sense to try to take the "fast path" in
SIDelExpiredDataEntries with only a shared lock rather than exclusive.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.



view thread (30+ messages)  latest in thread

Message-ID: <20080107151234.GG4723@alvh.no-ip.org>
Permalink:  ../20080107151234.GG4723@alvh.no-ip.org/
Also on:    postgresql.org/message-id/20080107151234.GG4723@alvh.no-ip.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: alvherre@commandprompt.com, kuba@comgate.cz, tgl@sss.pgh.pa.us
  Subject: Re: Linux/PostgreSQL scalability issue - problem with 8 cores
  In-Reply-To: <20080107151234.GG4723@alvh.no-ip.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox