Unfortunately we still see it frequently :( On 9 August 2017 at 14:29, Achilleas Mantzios <ach...@matrix.gatewaynet.com> wrote:
> On 09/08/2017 15:27, ADSJ (Adam Sjøgren) wrote: > >> On 2017-06-21 Adam Sjøgren <a...@novozymes.com> wrote: >> >> Adam Sjøgren <a...@novozymes.com> wrote: >>> >>>> Meanwhile, I can report that I have upgraded from 9.3.14 to 9.3.17 and >>>> the errors keep appearing the log. >>>> >>> Just to close this, for the record: We haven't seen the errors since >> 2017-06-30. We upgraded to 9.3.17 (latest 9.3 point-release at the time >> of writing) on 2017-06-10. >> >> Whether this means that the affected rows gradually got overwritten >> after switching to .17 and thus got fixed, or if something subtle in our >> workflow changed, so we aren't hitting this anymore, or something else >> entirely is the answer, we're not sure. >> > Glad you sorted it out! You have been consistent in your effort to chase > this down, and reverted back with your findings to close the case. Thumbs > up! > >> We didn't get to trying Alvaro Herrera's suggestion of removing >> 6c243f90ab6904f27fa990f1f3261e1d09a11853 before the errors stopped >> appearing "by themselves". >> >> >> Best regards, >> >> Adam >> >> > -- > Achilleas Mantzios > IT DEV Lead > IT DEPT > Dynacom Tankers Mgmt > > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
