# Percona Postgres: Primary promotion happened during parameter change and behavior during pod delete forcefully

**URL:** <https://forums.percona.com/t/percona-postgres-primary-promotion-happened-during-parameter-change-and-behavior-during-pod-delete-forcefully/40811>\
**Category:** Percona Distribution for PostgreSQL\
**Created:** [May 18, 2026, 11:07am UTC](https://forums.percona.com/t/percona-postgres-primary-promotion-happened-during-parameter-change-and-behavior-during-pod-delete-forcefully/40811 "2026-05-18T11:07:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Srinivas](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/srinivas/32/23606_2.png) [@Srinivas](https://forums.percona.com/u/Srinivas)\
**Post date:** [May 18, 2026, 11:07am UTC](https://forums.percona.com/t/percona-postgres-primary-promotion-happened-during-parameter-change-and-behavior-during-pod-delete-forcefully/40811/1 "2026-05-18T11:07:27Z")

</div>

Please clarify understanding to the below questions.

1. We changed the parameter “patroni.leaderLeaseDurationSeconds,” which triggered a pod restart one at a time for both the primary and replica pods. We also observed a failover, where the replica was promoted. Is this expected behavior?

2. We conducted a test case by forcefully deleting the pod and observed that the primary pod’s role remained unchanged after the restart, but the TimeLine was updated. Is this expected behavior?