Re: Update or Delete causes canceling of long running slave queries - Mailing list pgsql-general

From Jeff Janes
Subject Re: Update or Delete causes canceling of long running slave queries
Date
Msg-id CAMkU=1y42MqUgiQziVMR=qDH3GXA2oTVrkmQ8GeDDZH2HQzLDg@mail.gmail.com
Whole thread Raw
In response to Re: Update or Delete causes canceling of long running slave queries  (Viswanath <M.Viswanath16@gmail.com>)
Responses Re: Update or Delete causes canceling of long running slave queries
List pgsql-general
On Thu, May 12, 2016 at 9:22 PM, Viswanath <M.Viswanath16@gmail.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


pgsql-general by date:

Previous
From: Nicolas Paris
Date:
Subject: Re: [SPAM] COPY command & binary format
Next
From: Jeff Janes
Date:
Subject: Re: index on ILIKE/LIKE - PostgreSQL 9.2