Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130714
Precedence: list
MIME-Version: 1.0
Date: Thu, 30 Apr 2026 09:49:32 +0200
To: erictnorris@gmail.com
Cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] `COM_RESET_CONNECTION` support in `mysqlnd`
In-Reply-To: <CA+NMNO2WouLYZ9PKQSvdf=8s9WoJeod_PbwWdc6zQh8WUovhyg@mail.gmail.com>
References: <CA+NMNO2WouLYZ9PKQSvdf=8s9WoJeod_PbwWdc6zQh8WUovhyg@mail.gmail.com>
Message-ID: <3ff59f9b3d7a872dc0159651848dace8@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2026-04-27 20:09, schrieb Eric Norris:
> Personally, given that both of these versions are EOL, this feels
> acceptable, but I'm curious what others think.

I agree that it is a reasonable expectation from users to use the latest 
(or at least: a supported) version of third party software when they 
want to use the latest PHP version. Especially since my understanding is 
that in this instance, the communication would also not be broken 
entirely, but users would just need to disable persistent connections, 
no? This means if they want to upgrade PHP, without being able to 
upgrade their MySQL version they would potentially need to give up some 
performance optimization, but other than that it would work unchanged?

Somewhat relatedly, see: 
https://github.com/php/php-src/pull/21159#issuecomment-4111691063. I 
think it would be good to decide both cases at the same time, since they 
are reasonably similar.

Best regards
Tim Düsterhus