Alvaro Herrera wrote:
> Now that I actually check with a non-relation object, I see pretty much
> the same error. So probably if instead of some narrow bug fix what we
> need is some general solution for all object types. I know this has
> been discussed a number of times ... Anyway I see now that we should
> not consider this a backpatchable bug fix, and I'm not doing the coding
> either, at least not now.
Discussed this with a couple of 2ndQ colleagues and it became evident
that MVCC catalog scans probably make this problem much more prominent.
So historical branches are not affected all that much, but it's a real
issue on 9.4+.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
