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.96) (envelope-from ) id 1vvyEY-00D6xZ-2u for pgsql-general@arkaria.postgresql.org; Fri, 27 Feb 2026 13:50:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vvyEX-003abz-2V for pgsql-general@arkaria.postgresql.org; Fri, 27 Feb 2026 13:50:21 +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.96) (envelope-from ) id 1vvyEX-003abm-1M for pgsql-general@lists.postgresql.org; Fri, 27 Feb 2026 13:50:21 +0000 Received: from zimbra.optitool.de ([95.130.165.165]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vvyET-00000001VM3-2wGz for pgsql-general@lists.postgresql.org; Fri, 27 Feb 2026 13:50:20 +0000 Received: from zimbra.optitool.de (localhost [127.0.0.1]) by zimbra.optitool.de (Postfix) with ESMTPS id BDCBE305F33; Fri, 27 Feb 2026 14:50:15 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by zimbra.optitool.de (Postfix) with ESMTP id A6603305F3F; Fri, 27 Feb 2026 14:50:15 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.10.3 zimbra.optitool.de A6603305F3F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=optitool.de; s=E37AA3DA-415C-11E8-B16D-258E1F829521; t=1772200215; bh=lOUEAOslhjGsa8gBCHWT0l9CQXCE47L7Kd6wKA02S7Y=; h=Date:From:To:Message-ID:MIME-Version; b=UNeamV4Vfh29RLLMD+WAtHGBBwztmBsvEzsdtZkT2V5ZyRxuS8zJQyXf8SJ9cjn7Z GX3QNaHf3mLOxl/JzmqzuHNXklZhyARKBEYVj9AeAvq1iB6n/IdDgnlp1pIBQP/NTu VRdKouqk4B1G3layPfJ8Icg/ty4DnwsNGObEOglXlHnBX9Yr1oZsAaL6Eyz1t6zaN8 z5Imzi113DgKG3z76FSZ5qUJqBtxUUzf/oBED5jOb8n7HFxyV+B4zfrt/UxaYWl1ht 7YsbjdOK1mvDILd2BJREOKqJHp02XujQ2f2g0PdVA/ll6/EZSX0F4vynKosUv3jYbR uU15DJjuf0vgw== Received: from zimbra.optitool.de ([127.0.0.1]) by localhost (zimbra.optitool.de [127.0.0.1]) (amavis, port 10026) with ESMTP id iJrOUXssIQpZ; Fri, 27 Feb 2026 14:50:15 +0100 (CET) Received: from zimbra.optitool.de (localhost [127.0.0.1]) by zimbra.optitool.de (Postfix) with ESMTP id 8B28A305F3E for ; Fri, 27 Feb 2026 14:50:15 +0100 (CET) Date: Fri, 27 Feb 2026 14:50:15 +0100 (CET) From: Thomas Butz To: pgsql-general@lists.postgresql.org Message-ID: <1543587245.5930958.1772200215404.JavaMail.zimbra@optitool.de> Subject: Change WAL directory via conf MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 10.1.10_GA_1000 (ZimbraWebClient - FF148 (Linux)/10.1.10_GA_1000) Thread-Index: VjCEPsbmXNyASKTEDqFb/lkJ3KOu7w== Thread-Topic: Change WAL directory via conf List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Is there a reason why the location of the WAL directory cannot be specified via the configuration? The documentation describes a workaround using a symbolic link, which I find rather awkward: https://www.postgresql.org/docs/current/wal-internals.html Why is there no wal_directory analogous to data_directory? -- Thomas Butz