From: Roxanne Reid-Bennett <rox@tara-lu.com>
To: pgsql-performance@postgresql.org
Subject: Re: MusicBrainz postgres performance issues
Date: Sun, 15 Mar 2015 22:23:56 -0400
Message-ID: <55063EBC.5020405@tara-lu.com> (raw)
In-Reply-To: <B008F2EE-45D7-4535-9163-56A8CDCA553C@musicbrainz.org>
References: <B008F2EE-45D7-4535-9163-56A8CDCA553C@musicbrainz.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 3/15/2015 6:54 AM, Robert Kaye wrote:
> Hi!
>
> We at MusicBrainz have been having trouble with our Postgres install
> for the past few days. I’ve collected all the relevant information here:
>
> http://blog.musicbrainz.org/2015/03/15/postgres-troubles/
>
> If anyone could provide tips, suggestions or other relevant advice for
> what to poke at next, we would love it.
Robert,
Wow - You've engaged the wizards indeed.
I haven't heard or seen anything that would answer my *second* question
if faced with this (my first would have been "what changed")....
What is the database actually trying to do when it spikes? e.g. what
queries are running ?
Is there any pattern in the specific activity (exactly the same query,
or same query different data, or even just same tables, and/or same
users, same apps) when it spikes?
I know from experience that well behaved queries can stop being well
behaved if underlying data changes
and for the experts... what would a corrupt index do to memory usage?
Roxanne
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: rox@tara-lu.com
Subject: Re: MusicBrainz postgres performance issues
In-Reply-To: <55063EBC.5020405@tara-lu.com>
* 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