From: Tom Lane <tgl@sss.pgh.pa.us>
To: Arnd Baranowski <baranowski@oculeus.com>
cc: pgsql-bugs@postgresql.org
Subject: Re: PostgreSQL & latest Mac OS Sonoma,
 a possible bug / configuration issue
In-reply-to: <C87F1481-6A03-45E3-BE60-C55F568220C0@oculeus.com>
References: <C87F1481-6A03-45E3-BE60-C55F568220C0@oculeus.com>
Comments: In-reply-to Arnd Baranowski <baranowski@oculeus.com>
	message dated "Mon, 05 Feb 2024 20:03:32 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <269595.1707165898.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 05 Feb 2024 15:44:58 -0500
Message-ID: <269596.1707165898@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/269596.1707165898%40sss.pgh.pa.us>
Precedence: bulk

Arnd Baranowski <baranowski@oculeus.com> writes:
> I have a MacBook Pro 16 inch with M3 Max in the base configuration (48 g=
ig RAM, 1 terabyte HD). Operating System macOS the latest Sonoma 14.3. I u=
se the latest Postgres 14 installed via brew in the standard configuration=
. From time to time (every second or third week) I use to reboot the Mac a=
nd since several weeks now (the last 4 reboots at least) I lose data of th=
e database when rebooting and I fall back to a state of several days ahead=
 of the reboot. This affects structure and data added. I cover this via ba=
ckups and it looks that data is kept in memory rather than written to the =
database. Beside this Mac and Postgres run fine.

Hmm, what have you got the fsync and wal_sync_method GUCs set to?
What was the last macOS version that was stable for you?

			regards, tom lane