Delete Query slowdown Slave database.

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,

Re: Suddenly all queries moved to seq scan

> On 20 Nov 2024, at 6:32 PM, Daniel Gustafsson wrote: > >> On 20 Nov 2024, at 11:50, Sreejith P wrote: > >> We are using PostgresQL 10 in our production database. We have around 890 >> req /s request on peak time. > > PostgreSQL 10 is well out of support

Suddenly all queries moved to seq scan

Hi, We are using PostgresQL 10 in our production database. We have around 890 req /s request on peak time. We have 1 primary and 4 slave databases as well in the same postgres cluster. 2 days back we applied some patches in the primary server and restarted. We didn't do anything on the secondar

Check replication lag

Hi, Am using SELECT (now() - pg_last_xact_replay_timestamp()) < '1’) min for identifying replication lag. Is there any better option available in postgres 10. IN SYNC mode of replication what would be the impact on Master DB server in terms of over all performance ? Thanks Sreejith. --