| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Arnd Baranowski <baranowski(at)oculeus(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue |
| Date: | 2024-02-05 20:44:58 |
| Message-ID: | 269596.1707165898@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Arnd Baranowski <baranowski(at)oculeus(dot)com> writes:
> I have a MacBook Pro 16 inch with M3 Max in the base configuration (48 gig RAM, 1 terabyte HD). Operating System macOS the latest Sonoma 14.3. I use 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 and since several weeks now (the last 4 reboots at least) I lose data of the 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 backups 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arnd Baranowski | 2024-02-05 22:00:26 | Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue |
| Previous Message | Tom Lane | 2024-02-05 20:05:38 | Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe |