Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115966 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 3572 invoked from network); 6 Sep 2021 15:13:00 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 6 Sep 2021 15:13:00 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1797C1804AD for ; Mon, 6 Sep 2021 08:50:15 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS1836 195.49.0.0/17 X-Spam-Virus: No X-Envelope-From: Received: from darkcity.gna.ch (darkcity.gna.ch [195.49.47.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 6 Sep 2021 08:50:14 -0700 (PDT) Received: from smtpclient.apple (unknown [IPv6:2001:918:ff83::7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by darkcity.gna.ch (Postfix) with ESMTPSA id C6BCB151668F for ; Mon, 6 Sep 2021 17:50:11 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Date: Mon, 6 Sep 2021 17:50:11 +0200 References: <0A048A30-444F-4DB0-A79C-9EA9BD07B1EC@cschneid.com> <569E3A48-E3F5-46FA-BA08-D2493CE4FD33@cschneid.com> <9B6A493C-DBA6-4CF0-9AE2-DAA0A700A7D2@cschneid.com> <88103087-61a5-8f89-a146-0a77d8d28e84@gmx.de> To: PHP internals In-Reply-To: Message-ID: X-Mailer: Apple Mail (2.3654.120.0.1.13) Subject: Re: [PHP-DEV] Adding a way to disable the stat cache From: cschneid@cschneid.com (Christian Schneider) Am 06.09.2021 um 16:46 schrieb Pierre Joye : > Also as someone mentioned here afterwards, instead of removing it > straight away, I would go with the flag first, less risky :) Out of curiosity: Do you think disabling the stat cache could be = harmful? If no, why make it an option? If yes, should we be allowing it? Follow-up question: What would be the default? Cache off which might be harmful to some (assumedly bigger) sites? Cache on which won't fix the bug reports? If you put the burden on the bigger PHP users by making it default to = off you're assuming they have more rigorous update procedures, I guess. = Probably true, just make sure that it is mentioned prominently enough in = UPGRADING. Ok, I've said my piece :-) - Chris