--> But the right answer is to fix it on the writing side. Yes I agree with this part. Even though there is very low probability, a process can still be killed in middle when writing. So what is your suggestion on how to recover from this automatically?
On Fri, May 10, 2019 at 9:14 AM Tom Lane <t...@sss.pgh.pa.us> wrote: > neeraj kumar <neeru....@gmail.com> writes: > > Also curious why query on pg_stat_activity is considering terminated > > process ? > > The short answer to that is that this bug leaves shared memory in > a corrupt state. It's not really useful to worry about whether > readers should react differently to that --- you could spend endless > amounts of time hypothesizing different kinds of corruption and > endless amounts of code/cycles trying to work around it. But the > right answer is to fix it on the writing side. > > regards, tom lane > -- ------------------------------------- Thanks Neeraj Kumar, +1 (206) 427-7267
