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 1rUnrY-00D69r-4U for pgsql-general@arkaria.postgresql.org; Tue, 30 Jan 2024 13:09:16 +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 1rUnqZ-005VFF-AY for pgsql-general@arkaria.postgresql.org; Tue, 30 Jan 2024 13:08:15 +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 1rUnqZ-005VF7-0F for pgsql-general@lists.postgresql.org; Tue, 30 Jan 2024 13:08:15 +0000 Received: from mail.pernau.at ([176.9.98.135]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rUnqW-0049QP-6s for pgsql-general@lists.postgresql.org; Tue, 30 Jan 2024 13:08:13 +0000 Received: from pernau.at (localhost.localdomain [127.0.0.1]) by mail.pernau.at (Postfix) with ESMTPSA id B664F2FA5551 for ; Tue, 30 Jan 2024 14:08:09 +0100 (CET) MIME-Version: 1.0 Date: Tue, 30 Jan 2024 14:08:09 +0100 From: Klaus Darilion To: pgsql-general list Subject: Write Logical Replication Spill Files to different volume Message-ID: X-Sender: klaus.mailinglists@pernau.at Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello! If I understand it right, the logical replication .spill files in the pg_replslot subfolders are temporary files that need not survive server crashes (as on postgresql restart the WAL senders will delete old spill files, start again reading WAL and regenerate the spill files if necessary). For big transactions with plenty of replication slots, the spill files may consume plenty of disk space. I think it would be useful to have the spill files on a different disk, ie the "normal" database files and the pg_replslot status file are on a high available volume (DRBD, shared storage ...) whereas the spill files are only on local disks. Is this already possible? If not, are there reasons why that should not be done? thanks Klaus