Wednesday, 24 September 2025

Filled under:

 “Good [morning/afternoon] everyone,

I’d like to share about the PostgreSQL BCM automation we’ve implemented.

This automation provides the ability to perform a plain switchover of the database whenever a user requests it. The user simply raises a ticket and specifies the desired site, and that site automatically becomes the new leader.

Before the switchover happens, the automation performs important checks — like verifying if the site is really a member of the cluster, ensuring the cluster is healthy, and confirming that replication lag is zero.

This has proven to be extremely useful — not just during BCM tests, but also in day-to-day operations. Earlier, users had to raise incident channels, wait for a DBA, and go through manual steps. Now, the automation handles everything quickly and safely.

The benefits are clear: it saves DBA time, reduces dependency on manual intervention, and improves user experience by avoiding delays.

In short, PostgreSQL BCM automation makes the switchover process faster, safer, and more user-friendly.”



“With this automation, we’ve turned a complex process into a simple request. And with that, I’ll hand it over to [Name] to take you through the next part.”


Confident tone:

“In short, less waiting, less manual effort, and more efficiency. On that note, let me pass it over to

 [Name].”




Posted By Nikhil01:06

Wednesday, 17 September 2025

ranjit

Filled under:

  wanted to ask for a quick chat to clear up a few things that have been on my mind recently. There are a couple of situations I think we could discuss to make sure we're on the same page and avoid any misunderstandings going forward.

Posted By Nikhil05:47

Friday, 12 September 2025

Filled under:

 Occasional check-ins on workload balance would help ensure I can deliver effectively.


More opportunities for involvement in decision-making would make me feel more engaged.


Clearer communication on priorities and upcoming changes would help me focus better. At times, there are duplicate communications through email and multiple chat groups on items that may not be top priority. Streamlining these updates and focusing discussions on key priorities would allow me to spend more time on execution rather than managing overlapping communicati

ons.

Posted By Nikhil00:26

Saturday, 6 September 2025

Filled under:

 Thanks for assigning this last night. As the mail came at the last moment with limited details, and I was already engaged with other priority tasks today, I couldn’t manage the bandwidth to take up the manual patching.

Please let me know if you’d like me to pick this up on Sunday, or if you will be able to handle it when you log in, as I see from the other emails that the patching window for this DB is open until 7 PM.

Posted By Nikhil01:04

Monday, 1 September 2025

Filled under:

 

The recent issue was due to a toolkit update that included iptables changes. This resulted in certain IP blocking within the cluster and on 2 nodes outside the cluster. As a consequence, Patroni detected the cluster as unhealthy and attempted to identify a healthy candidate for switchover, but was unable to do so, leading to a Leader restart.

Subsequently, resiliency was partially impacted, and the 2 affected nodes were later brought back in sync under CHANGE_NUMBER123.

Posted By Nikhil23:42

N

Filled under:

 Hey there! Thanks for reaching out.

If I miss your message, please drop an email to the Ops team at [team email] so we don’t miss it.

Appreciate your patience 🙏

Posted By Nikhil20:26