将 PHP 5.2.5 升级到 5.2.6 会导致任何问题吗？
我们目前运行的是 php 5.2.5。 我们现在遇到了一个导致段错误的错误。 我们对该解决方案的第一个想法是升级到版本 5.2.6，但对它会产生的问题持怀疑态度。 我们正在运行 Apache 并托管十几个站点。
- 现有的代码会被破坏吗？
- 是否有任何重大变化需要注意。 我正在阅读更改日志，但没有注意到任何内容。
- 如果出现问题是否可以轻松恢复到 5.2.5？
- 还有什么需要注意的吗？
We're currently running with php 5.2.5. We have now encountered a bug that creates a seg fault. Our first idea at the solution is upgrading to version 5.2.6 but are skeptical of problems that it will create. We are running Apache and host a dozen or so sites.
- Will any existing code break?
- Are there any significant changes to be aware of. I was reading the change log but didn't notice any.
- Is it easy to revert back to 5.2.5 if something goes wrong?
- Anything else to be aware of?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
感谢大家的意见。 获得测试服务器肯定是在路线图上。 这应该是最终获得一个设置的一个很好的论据。 我们是一家足够小的公司，我们可以轻松地只拥有一台服务器，但拥有测试服务器有很多优势。
不幸的是，如果不升级的话，这个项目将很难继续前进，而且我怀疑是否有时间进行测试环境。
Thanks for everyone's input. Getting a test server is definitely on the road map. This should be a good argument for finally getting one setup. We're a small enough company where we could easily get away with only having one, but there are so many advantages to having a test server.
Unfortunately it will be hard to get this project moving forward without upgrading and i doubt there will be time for a test environment.
正如大家所说，只有测试才能确定。 然而，像这样的小版本更新很少会导致兼容性问题。
无论如何，这里是更改说明。
但从长远来看，您将不得不在某个时候进行升级，否则就会面临暴露于已知安全漏洞的风险。
As everyone is saying, only testing will tell you for sure. However, minor version updates like this will only rarely cause compatibility problems.
For what it's worth, here are the change notes.
In the long run though, you will have to upgrade at some point or risk being exposed to known security vulnerabilities.
很可能不会。 从 5.2.5 到 5.2.6 的跳跃很小，它是一个错误修复版本（请参阅 变更日志）。
但每当升级任何内容时，请确保在将代码投入生产之前在开发环境中测试代码。
Most likely not. The jump from 5.2.5 to 5.2.6 is small, it is a bug-fix release (see the changelog).
But whenever upgrading anything, make sure to test your code in a dev environment before putting it into production.
如果不先对其进行分析，我们中的任何人都不可能对现有的代码破坏做出明确的肯定或否定的回答。
这正是测试环境的用途。 如果您设置了测试环境，则可以执行升级，然后进行回归测试以查看是否有任何问题。 没有这个环境，你就是在赌博。
@Grant Wagner：关于虚拟化的重要观点。 设置良好的测试环境并不困难。
It's impossible for any of us to say definitely yes or no about your existing code breaking without performing an analysis on it first.
This is exactly what test environments are for. If you have a test environment set up, you can perform the upgrade, then do regression testing to see if anything breaks. Without this environment, you're making a gamble.
@Grant Wagner: Great point on virtualization. Setting up a good test environment doesn't have to be difficult.
使用现代虚拟机选项VMware Server，Microsft 虚拟服务器，Microsoft Virtual PC 等，为什么不建立一个运行现有平台的虚拟环境，然后升级并测试它呢？
如果您愿意花钱，您可以购买进行 P2V（物理到虚拟）的工具，该工具将采用您现有的设置并为您提供它的虚拟化副本（如果您已经做了很多工作，这可能很有价值）对可能难以生成与原始版本足够匹配以进行适当测试的虚拟化版本的配置进行自定义）。
With modern Virtual Machine options VMware Server, Microsft Virtual Server, Microsoft Virtual PC and others, why not set up a virtual environment running your existing platform, then upgrade and test that?
If you are willing to spend money, you can buy tools to do P2V (Physical-to-Virtual) that will take your existing setup and provide you with a virtualized copy of it (this could be valuable if you've done a lot of customization to the configuration that might be difficult to produce to a virtualized version that matches the original well enough to do proper testing).