Hi,
Tom Lane wrote:
I hope you're not expecting the contents of shared memory to still be
trustworthy after a backend crash.
Hm.. that's a good point.
So I either need to bullet-proof the imessages with checksums or some
such. I'm not sure that's doable reliably. Not to speak about performance.
Thus it might be better to just restart the replication manager as well.
Note that this means leaving the replication group temporarily and going
through node recovery to apply remote transactions it has missed in
between. This sounds expensive, but it's certainly the safer way to do
it. And as such backend crashes are Expected Not To Happen(tm) on
production systems, that's probably good enough.
If the manager is working strictly
from its own local memory, then it would be reasonable to operate
as above.
That's not the case... :-(
Thanks for your excellent guidance.
Regards
Markus
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
