Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130718
Precedence: list
MIME-Version: 1.0
References: <CA+NMNO2WouLYZ9PKQSvdf=8s9WoJeod_PbwWdc6zQh8WUovhyg@mail.gmail.com>
 <3ff59f9b3d7a872dc0159651848dace8@bastelstu.be>
In-Reply-To: <3ff59f9b3d7a872dc0159651848dace8@bastelstu.be>
Reply-To: erictnorris@gmail.com
Date: Thu, 30 Apr 2026 10:11:58 -0400
Message-ID: <CA+NMNO2Y=BjuiP84Kv+4MUMTo2-EHrz8HwO5bViJRw-b9Mt8cg@mail.gmail.com>
Subject: Re: [PHP-DEV] `COM_RESET_CONNECTION` support in `mysqlnd`
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: eric.t.norris@gmail.com (Eric Norris)

On Thu, Apr 30, 2026 at 3:49=E2=80=AFAM Tim D=C3=BCsterhus <tim@bastelstu.b=
e> wrote:
>
> 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?

That's a great point, and correct - users can still upgrade, they just
will need to give up persistent connections.

>
> 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.

That could make sense, and how would you suggest we proceed to decide
the case? I'll admit that I'd be hesitant to need to resolve that via
an RFC, since if the RFC failed I'd need to potentially make another
RFC just for my change + some INI setting, and so it'd be quite some
time until I could get this merged. That's not to say we shouldn't do
it, I'm just noting my hesitation.