Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110330
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
In-Reply-To: <CA+p1FabH1rL48z=QNP8324WNmaJvAN=skfWi7b9NCnpU5MVHag@mail.gmail.com>
Date: Mon, 1 Jun 2020 21:47:13 +0200
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <843C9840-7AFD-4A8F-9C90-06DC1882AB05@cschneid.com>
References: <CA+p1FabH1rL48z=QNP8324WNmaJvAN=skfWi7b9NCnpU5MVHag@mail.gmail.com>
To: David Gebler <davidgebler@gmail.com>
Subject: Re: [PHP-DEV] RFC proposal: fsync support for file resources
From: cschneid@cschneid.com (Christian Schneider)

Am 01.06.2020 um 18:56 schrieb David Gebler <davidgebler@gmail.com>:
> It seems to me an odd oversight that this has never been implemented =
in PHP
> and means PHP has no way to perform durable file write operations, =
making
> it inherently unsuitable for any systems requiring more intensive I/O,
> mission critical logs, auditing, etc.

I think there is a misconception of the usefulness of fsync() here.

First of all it does not *really* guarantee the data is safe from power =
outages etc, see
	https://stackoverflow.com/a/706688
	https://stackoverflow.com/a/725742
and other answers in that thread.

Secondly I'd rather rely on something like a proper DB if not losing any =
data is crucial.
Trying to implement it in pure PHP and plain old files seems like using =
the wrong tools for the job to me.

While there is little reason not to add fsync() to PHP the importance =
and benefits are IMHO not that big.

- Chris