Re: Update or Delete causes canceling of long running slave queries

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Viswanath <M(dot)Viswanath16(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Update or Delete causes canceling of long running slave queries
Date: 2016-05-14 15:59:21
Message-ID: CAMkU=1y42MqUgiQziVMR=qDH3GXA2oTVrkmQ8GeDDZH2HQzLDg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 12, 2016 at 9:22 PM, Viswanath <M(dot)Viswanath16(at)gmail(dot)com> wrote:
> Hi,
> Thank you for the explanation.
> The slave queries are mostly reporting queries,which sometimes would take
> 30+ running time due to complex joins and criteria. We haven't tried running
> these queries on master before splitting, and it is possible that there will
> be heavy updates and deletes on master on some tables some times. Now we
> have to decide between these two parameters as which one to use. Can you
> give any suggestion?

I would go with hot_standby_feedback = on, and look for other
solutions only if that is demonstrated to cause a problem (like severe
bloat) under your workload.

Cheers,

Jeff

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Janes 2016-05-14 17:13:16 Re: index on ILIKE/LIKE - PostgreSQL 9.2
Previous Message Nicolas Paris 2016-05-14 13:47:07 Re: [SPAM] COPY command & binary format