Delete Query slowdown Slave database. - Mailing list pgsql-general

From Sreejith P
Subject Delete Query slowdown Slave database.
Date
Msg-id A53FF53D-8578-4271-ACCD-8C647FE93F53@lifetrenz.com
Whole thread Raw
List pgsql-general
Hello,

My doubt here is, in a master - slave (streaming replication) set up, when I run a long running delete query for deleting 80 million records, . All queries in slave started running 2- 5 mins all of a sudden. When I check SQL analyse, most of the queries, planner used to choose seq scan, instead of seq scan. 

What could be the possibility?

How delete query running in Master affect secondary(Slave) DB.

Is it related to shared memory ?


NB: Problem solved after restarting slave servers. 



Thanks
Sreejith


 

Solutions for Care Anywhere


dWise HealthCare IT Solutions Pvt. Ltd. | www.lifetrenz.com
Disclaimer: The information and attachments contained in this email are intended for exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender immediately and destroy all copies of this message and any attachments. The views expressed in this email are, unless otherwise stated, those of the author and not those of dWise HealthCare IT Solutions or its management.

pgsql-general by date:

Previous
From: Bertrand Mamasam
Date:
Subject: Re: ERROR wrong varnullingrels (b 3) (expected (b)) with LEFT JOIN LATERAL and CTE
Next
From: Tom Lane
Date:
Subject: Re: ERROR wrong varnullingrels (b 3) (expected (b)) with LEFT JOIN LATERAL and CTE