On Tue, Jul 03, 2018 at 01:51:48PM -0400, Alvaro Herrera wrote:
> Getting this fixed is +0.2 from me -- I'm not really on the side of this
> being a severe bug as all that.
This can also cause incorrect results for clients querying
pg_replication_slots when measuring bloat in pg_wal/, hence as this
thing is new I would think that restricting the API first, and then
perhaps relaxing it with future improvements makes the most sense.
--
Michael
