Re: Stalls on PGSemaphoreLock - Mailing list pgsql-performance

From Emre Hasegeli
Subject Re: Stalls on PGSemaphoreLock
Date
Msg-id CAE2gYzybbrAOakC-CuomQf7SacZtZzH_xQV6F06uCN6=q8+MZQ@mail.gmail.com
Whole thread Raw
In response to Stalls on PGSemaphoreLock  (Matthew Spilich <mspilich@tripadvisor.com>)
List pgsql-performance
2014-03-25, Matthew Spilich <mspilich@tripadvisor.com>:

Has any on the forum seen something similar?   Any suggestions on what to look at next?    If it is helpful to describe the server hardware, it's got 2 E5-2670 cpu and 256 GB of ram, and the database is hosted on 1.6TB raid 10 local storage (15K 300 GB drives).   The workload is predominantly read and the queries are mostly fairly simple selects from a single large table generally specifying the primary key as part of the where clause along with a few other filters.  

I have seen something similar. It was because of
large shared_buffers.

pgsql-performance by date:

Previous
From: Matthew Spilich
Date:
Subject: Re: Stalls on PGSemaphoreLock
Next
From: Takashi Horikawa
Date:
Subject: Re: Stalls on PGSemaphoreLock