Re: Puzzling full database lock

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Christopher Opena <counterveil(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Puzzling full database lock
Date: 2012-02-06 14:34:56
Message-ID: CAHyXU0wHT7dKY5Bs9tpD5rRg_z9YdK=yMc_q0qTahotAqQHFDA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Feb 3, 2012 at 2:55 PM, Christopher Opena <counterveil(at)gmail(dot)com> wrote:
> Merlin, thanks for the response.

no problem. if you're open to architecture suggestions you might also
want to consider going with HS/SR and getting those large olap queries
off your main database. you'll have to configure it to be very
forgiving of long running queries (which can pause replication) but
this should be a huge win in terms of total load on the main server.
also, you can skimp on hardware to a certain degree to cut costs. we
still want to get to the bottom of this obviously but it can't hurt to
get a plan 'B' going...

merlin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2012-02-06 15:23:19 How to create crosstab with 3 values in every crosstab column
Previous Message Fanbin Meng 2012-02-06 13:52:23 Backup database remotely