Re: [RFC] [VOTE] Minimum supported versions for PHP 8.6
| From: | Alexander Kurilo | Date: | Thu, 16 Jul 2026 19:46:46 +0000 |
| Subject: | Re: [RFC] [VOTE] Minimum supported versions for PHP 8.6 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-131981@lists.php.net to get a copy of this message | ||
On 2026-07-16 17:22, Eric Norris wrote:
Hello all, I'm announcing the start of the vote for the "Minimum supported versions for PHP 8.6" RFC. The voting will end at 2026-07-30 15:48:00 UTC. There are multiple votes, one for each minimum version requirement. RFC: https://wiki.php.net/rfc/min_supported_versions_php_8_6 Discussion: https://news-web.php.net/php.internals/131707 Thanks! EricI'm sorry to bring this up now (I missed the discussion phase) but is there a reason to make
COM_RESET_CONNECTION mandatory? I clearly see the upside of using it but it's a backward compatibility break that I find hard to justify:
1. If someone relied on the persistent connection state (for whatever reason that we might not see as the right technical choices, but still), the behavior of their application will appear silently broken.
2. If someone still uses an older MariaDB/MySQL, they'll get a significant performance penalty: their persistent connections will silently turn to non-persistent. And we're not talking about a decade-old databases!
If it were made optional, looks like both sides win: whoever interested, can opt in and stop worrying about mutable connection state, and those who can't do it because they have to use an older DB have one headache less: the RFC leaves them with few disappointing alternatives such as to accept the worse performance or not upgrade PHP.
Please correct me if I misunderstood the behavior you propose.
Cheers,
Alex