Bridget Frey <bridget.f...@redfin.com> writes:
> I just wanted to say thanks to everyone who has been working so hard on
> this issue. I realize it's not certain that this would fix the issues
> we're seeing, but we'd be willing to try it out and report back. The only
> caveat is we would need to deploy it to production, so if someone could let
> us know what the risk factor is here (e.g. the potential to make things
> worse), that would help us plan out how and when we would want to try it.
AFAICS the proposed patch is totally safe; it can't make things worse,
and should save some cycles to boot. Whether it fixes what you're
seeing is a different question of course, but testing would be mighty
helpful for that.
What I would actually ask about as far as production risk goes is
whether you are accustomed to building from patched sources. If you're
not, the risk of dropping a stitch in the build process could be
significant.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
