Re: Postgres 16 unexpected shutdown

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: postgres(at)arcict(dot)com
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Postgres 16 unexpected shutdown
Date: 2025-02-25 14:07:40
Message-ID: CAKAnmmLzTpJz9AiTtURfNwL0VH5m3TURSkJeUB+sGQ1kZSui1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Feb 25, 2025 at 8:51 AM <postgres(at)arcict(dot)com> wrote:

> Does this sound familiar anyone? Any ideas what might prompt Postgres to
> stop?
>

Postgres needs full read and write access to its own data directory. If it
doesn't, it will eventually PANIC, as your logs show.

See if you can figure out what else happened around 2025-02-22 08:05:49.427
CET, which seems to be when the problem started according to your logs.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Олег Самойлов 2025-02-25 14:15:15 How to return seto records from seof record function?
Previous Message postgres 2025-02-25 13:51:25 Postgres 16 unexpected shutdown