Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r1EAS-00A6C3-PO for pgsql-docs@arkaria.postgresql.org; Thu, 09 Nov 2023 23:10:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r1EAQ-00HPvm-8k for pgsql-docs@arkaria.postgresql.org; Thu, 09 Nov 2023 23:10:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r1EAQ-00HPve-0o for pgsql-docs@lists.postgresql.org; Thu, 09 Nov 2023 23:10:30 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r1EAN-004oLj-7c for pgsql-docs@lists.postgresql.org; Thu, 09 Nov 2023 23:10:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc: Content-ID:Content-Description; bh=75bPABk97pNhyooCzn+CZgWoOc+fqVhnOSx4IM18ZIk=; b=cg9dXNqKYHOLMHarwba7rW2C/D WjjXPUNvUBwi0x7wQwXVzS2g6jYplxAvzI9EeYNznZ/s2KvInHr5l+nMsozS71tUK+3sLgeoztWnw ITidT8dZ0+8gSAZSEgPtDq5NUO7fzyk1OqmxEW43KnuuVrr8pOf+M6TOpJgn1XKhZAsIk7EmSSbGm J8gBMyGkN1q0hwB3fnqNzYhLTO81T4GgEfVrlhD2XguUm0II++Bq/cFNOPzvsEYaExY3RbNXfGVPT /Ng4KNEB5Ml30NIOGewfBNonAX+njpslIpSk3ypKR7JuxsQM19ZQsx4sux2tL0uzxQ9TsgBPuK+cq M+VaqJMg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1r1EAM-002yeB-0f; Thu, 09 Nov 2023 18:10:26 -0500 Date: Thu, 9 Nov 2023 18:10:26 -0500 From: Bruce Momjian To: chris@cogdon.org, pgsql-docs@lists.postgresql.org Subject: Re: Typo in documentation - runtime-config-wal Message-ID: References: <155026029174.22710.10999038028707657619@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <155026029174.22710.10999038028707657619@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Feb 15, 2019 at 07:51:31PM +0000, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/runtime-config-wal.html > Description: > > This page: https://www.postgresql.org/docs/10/runtime-config-wal.html > (And probably others in other versions) has – I believe – an error in the > description for "wal_writer_delay". > > It says "woken up by an asynchronously committing transaction". I suspect > that should read "synchronously". Uh, is this correction accurate? It seems so to me. After flushing WAL the writer sleeps for the length of time given by wal_writer_delay, unless woken up sooner --> by an asynchronously committing transaction. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.