ffective.
> Please suggest the needful.
>
As mentioned above, I suggest asking only PostgreSQL related questions
on these mailing lists.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
as a different value on standby,
then it is possible that the decision whether a particular item is
dead differs on master and standby.
> (I wonder though why, if you executed the same query on the master,
> its setting of the index-entry-is-dead bits didn't propagate to the
>
ctual_variable_range execution that considerately slows down planning.
>
> Is it bug or restriction of implementation or misconfiguration of
> WAL/replication?
>
It is not a misconfiguration issue.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
standby role? It would be of great help, if you can direct me to any
> references details. Thank you, upfront.
>
I think pg_rewind can help in such situations. See the docs of pg_rewind [1].
[1] - https://www.postgresql.org/docs/devel/app-pgrewind.html
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
fine with that. Feel free to propose a patch on -hackers. I can
help in reviewing and improving the same.
--
With Regards,
Amit Kapila.
