Re: BUG #16874: Postgres Server crashes at commit

Thomas Trenz <thomas.trenz@jdisc.com>

From: Thomas Trenz <thomas.trenz@jdisc.com>
To: Michael Paquier <michael@paquier.xyz>, Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Date: 2021-02-22T07:17:10Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix concurrency issues with WAL segment recycling on Windows

Hi Michael,

just another hint. I downgraded the Postgres database to 12.6 again and 
I don't see those issues anymore in the log files on the same machine 
with the exact same configuration. Is there anything I can do to improve 
logging, check processes when using 13.2 so that you can easier isolate 
the root cause?

Mit freundlichen Grüßen/Best regards,

Thomas Trenz
*JDisc GmbH*

Tel.: +49-7034-9992-1041
Mobil: +49-171 2178419

*JDisc* GmbH
Kuppinger Weg 25
71116 Gärtringen

Twitter <https://twitter.com/jdisc3> | Blog <https://blog.jdisc.com>| 
LinkedIn <https://www.linkedin.com/in/thomas-trenz-99430a8/>| Xing 
<https://www.xing.com/profile/Thomas_Trenz2/cv>| WEB <https://www.jdisc.com>

P.S.: Register here <https://www.jdisc.com/en/newsletter.html> to 
receive our quarterly Newsletter

Am 20/02/2021 um 02:23 schrieb Michael Paquier:
> On Fri, Feb 19, 2021 at 12:28:54PM -0600, Merlin Moncure wrote:
>> On Fri, Feb 19, 2021 at 4:01 AM PG Bug reporting form
>> <noreply@postgresql.org> wrote:
>>> 2021-02-16 08:05:55.660 CET [5508] LOG:  could not rename file
>>> "pg_wal/000000010000000000000001": Permission denied
>> How did you upgrade or install this server? what is the platform?
> EACCES could come from an antivirus looking at the data folder,
> running concurrently with the server.
> --
> Michael