Delete Query slowdown Slave database.

From: Sreejith P <sreejith(at)lifetrenz(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Delete Query slowdown Slave database.
Date: 2024-11-28 18:25:31
Message-ID: A53FF53D-8578-4271-ACCD-8C647FE93F53@lifetrenz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 <http://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.

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2024-11-28 18:51:02 Re: ERROR wrong varnullingrels (b 3) (expected (b)) with LEFT JOIN LATERAL and CTE
Previous Message Bertrand Mamasam 2024-11-28 17:29:01 Re: ERROR wrong varnullingrels (b 3) (expected (b)) with LEFT JOIN LATERAL and CTE