pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Johannes Truschnigg <johannes@truschnigg.info>
To: John Scalia <jayknowsunix@gmail.com>
Cc: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Logical replication and wal segment retention
Date: Wed, 27 Feb 2019 14:38:58 +0100
Message-ID: <20190227133857.dvtswpk47aekermm@vault.lan> (raw)
In-Reply-To: <75D08FE7-36EC-4721-9382-DF8AF508644D@gmail.com>
References: <695C083D-AFB5-431B-B022-ED442CE94794@gmail.com>
	<20190227125242.6ixy4jkzcuj55cdl@vault.lan>
	<59567e0a-78e4-ed1c-f5b1-033aafcfb68a@matrix.gatewaynet.com>
	<75D08FE7-36EC-4721-9382-DF8AF508644D@gmail.com>

On Wed, Feb 27, 2019 at 08:29:09AM -0500, John Scalia wrote:
> I thought as much. The basic problem, however, is that I never created the
> logical slots. The IIDR application did that all by itself, and after it
> terminated, it did not bother to remove the slots. So, my disk monitor threw
> up when the WAL file system began to fill up. I was trying then to figure
> out why it did that.

I don't know the particular product that made you experience these troubles,
but it could be on purpose (if it relies on consuming the WAL continuously,
like a proper streaming replication slave/secondary would, and expectes to be
able to continue working where it left off before terminating) - or it could
be a rather dangerous usability hurdle that should, at the very least, be
clearly documented.


-- 
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )

www:   https://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp:  johannes@truschnigg.info

Please do not bother me with HTML-email or attachments. Thank you.

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (7+ messages)  latest in thread

Message-ID: <20190227133857.dvtswpk47aekermm@vault.lan>
Permalink:  ../20190227133857.dvtswpk47aekermm@vault.lan/
Also on:    postgresql.org/message-id/20190227133857.dvtswpk47aekermm@vault.lan

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: johannes@truschnigg.info, jayknowsunix@gmail.com, achill@matrix.gatewaynet.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Logical replication and wal segment retention
  In-Reply-To: <20190227133857.dvtswpk47aekermm@vault.lan>

* 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