Re: Detecting skipped data from logical slots (data silently skipped) - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Detecting skipped data from logical slots (data silently skipped)
Date
Msg-id 20160816211837.ebcewvxnedsesfmy@alap3.anarazel.de
Whole thread Raw
In response to Re: Detecting skipped data from logical slots (data silently skipped)  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Detecting skipped data from logical slots (data silently skipped)  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On 2016-08-08 10:59:20 +0800, Craig Ringer wrote:
> Right. Though if we flush lazily I'm surprised the effect is that big,
> you're the one who did the work and knows the significance of it.

It will be. Either you're increasing bloat (by not increasing the
slot's wal position / catalog xmin), or you're adding frequent syncs on
an idle connection.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [GENERAL] C++ port of Postgres
Next
From: Rahila Syed
Date:
Subject: Re: Surprising behaviour of \set AUTOCOMMIT ON