On 2018-02-21 10:08:12 -0500, Tom Lane wrote:
> Victor Yegorov <vyegorov@gmail.com> writes:
> > Is it possible, that bug #14852 is of the same nature as the issue at hand
> > here?
> > https://postg.es/m/20171013115320.28049.86457@wrigleys.postgresql.org
>
> For the archives' sake, the correct link is
> https://www.postgresql.org/message-id/20171013115320.28049.86457@wrigleys.postgresql.org
Yea, it does.
> Yeah, that does look suspiciously like a set of facts matching this
> problem :-(
I'd personally say ;), given that it's one less potentially data
corrupting bug to worry about ;). And it's one that can be fixed without
dataloss to boot.
Greetings,
Andres Freund