pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Klaus Darilion <klaus.mailinglists@pernau.at>
To: pgsql-general list <pgsql-general@lists.postgresql.org>
Subject: Write Logical Replication Spill Files to different volume
Date: Tue, 30 Jan 2024 14:08:09 +0100
Message-ID: <ccaeb39db549003abec2d1a626404d4f@pernau.at> (raw)

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






Message-ID: <ccaeb39db549003abec2d1a626404d4f@pernau.at>
Permalink:  ../ccaeb39db549003abec2d1a626404d4f@pernau.at/
Also on:    postgresql.org/message-id/ccaeb39db549003abec2d1a626404d4f@pernau.at

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: klaus.mailinglists@pernau.at
  Subject: Re: Write Logical Replication Spill Files to different volume
  In-Reply-To: <ccaeb39db549003abec2d1a626404d4f@pernau.at>
  References: <ccaeb39db549003abec2d1a626404d4f@pernau.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox