Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lE6hQ-0000pP-2g for pgsql-bugs@arkaria.postgresql.org; Mon, 22 Feb 2021 08:36:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lE6hL-00037A-Dv for pgsql-bugs@arkaria.postgresql.org; Mon, 22 Feb 2021 08:36:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lE5TH-00029j-GQ for pgsql-bugs@lists.postgresql.org; Mon, 22 Feb 2021 07:17:31 +0000 Received: from mail-wm1-x332.google.com ([2a00:1450:4864:20::332]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lE5TA-0006jq-Bd for pgsql-bugs@lists.postgresql.org; Mon, 22 Feb 2021 07:17:30 +0000 Received: by mail-wm1-x332.google.com with SMTP id o82so12512087wme.1 for ; Sun, 21 Feb 2021 23:17:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jdisc-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to; bh=FNg8ewxFSGpoAvmRYGHuC6N8KjczgzCBOFAG4En7ix8=; b=Y6fPgIys0ZScaf1UDWrkmxaI+DYTG2m4J9309gZTKYaLb25aGDFDn7cu1He4oVyrTI xF+L1FK+Y/3ax8pFuAtBaak/UnIaltXDRnCk7JOIVMPzyU4AgrW4hG1ovQJHbSev1bPO ZzqGrKEi/eQEYBVmrI9Fy4knTe9XEeaOST9lYvIskyWxYEIrOwI4nbg9Ta4dIot54gJj RBUIMSAReYHlZMXdT42z8nYP1F6inKkrF/IV8DFclIQKDmh44tFyQJ+BCiVUM6sr05WH kvcLt9oz2zYVBEjnsSa4nJA+tum3FLpMbyZtqbP1BposVr5/1Rs8U6PmLVRdwqDAUftg 0Pcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=FNg8ewxFSGpoAvmRYGHuC6N8KjczgzCBOFAG4En7ix8=; b=rVeE2IEh7sATlcr5PkFmGjxI8VzjThMX7vO7M7ecw4Tz59YDlS+y5228GOQFvnPYTl 44qlkbO9bNm+zAznIdPEhTiRIDK3B9l1choChkZ0FfJvTk4rRMf+Lv0DHoOn5FMB1CTs d+X/DkI+9tYnoxKgOWvwWbNLq0bLjYxQxOq9yWm/BG3jphjuHykTBz2DPBxzGsHU3ECk BHAGMaFAnuZAP5s82wzdFwtHZjz237Ymb6W0hVShRElT5gBX4ixnghj8IE3gbFvE2kUL Aq4Bq28ZYCRWvvQGL5en2SwvS/lrGOQ2DGzFt768VgAEog2QY+HUBx+FuVi23GbB6swZ fUGg== X-Gm-Message-State: AOAM532MkDtntxldPqV5rzCyDQZnf/u8WKcIaqDa+Tc79j8S/Ey1QBkE FnDUpr4oLroq1rLBjc103UvlCDugaznossPX X-Google-Smtp-Source: ABdhPJzlCr0xH+S6tKj7wHbgJYRIl4EpZZ+7QeZXsUhRH0PdJw2pWTqVK1BEtYf1HuGMTUvpSNLYLQ== X-Received: by 2002:a05:600c:4fd6:: with SMTP id o22mr3614679wmq.91.1613978242384; Sun, 21 Feb 2021 23:17:22 -0800 (PST) Received: from [192.168.178.26] (p4fd01482.dip0.t-ipconnect.de. [79.208.20.130]) by smtp.gmail.com with ESMTPSA id h12sm33486277wru.18.2021.02.21.23.17.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 21 Feb 2021 23:17:21 -0800 (PST) Subject: Re: BUG #16874: Postgres Server crashes at commit To: Michael Paquier , Merlin Moncure Cc: pgsql-bugs References: <16874-c3eecd319e36a2bf@postgresql.org> From: Thomas Trenz Organization: JDisc GmbH Message-ID: Date: Mon, 22 Feb 2021 08:17:10 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------3963F670947A2909F8CD66BE" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------3963F670947A2909F8CD66BE Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit 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 | Blog | LinkedIn | Xing | WEB P.S.: Register here 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 >> 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 --------------3963F670947A2909F8CD66BE Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit 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 | Blog | LinkedIn | Xing | WEB

P.S.: Register here 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

--------------3963F670947A2909F8CD66BE--