Re: BUG: *FF WALs under 9.2 (WAS: .ready files appearing on slaves)

From: Dennis Kögel <dk(at)neveragain(dot)de>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>
Subject: Re: BUG: *FF WALs under 9.2 (WAS: .ready files appearing on slaves)
Date: 2015-01-02 11:38:05
Message-ID: B8903B50-A6FA-4A62-BE59-FC5F3980719C@neveragain.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Am 31.12.2014 um 11:40 schrieb Michael Paquier <michael(dot)paquier(at)gmail(dot)com>:
>> As long as master is fixed, I don't actually care. But I agree with Dennis
>> that it's hard to see what's been commited with all the different issues
>> found, and if any commits were done, in which branch. I'd like to be able to
>> tell my customers: update to this minor release to see if it's fixed, but I
>> can't even do that.
> This bug does not endanger at all data consistency as only old WAL
> files remain on the standby, so I'm fine as well with just a clean fix
> on master, and nothing done on back-branches.

I’d like to point out that this issue is causing severe disk space bloat over time, as described in my previous posting. I’d assume that, as time goes by, this issue will pop up more and more, as long as back-branches remain unfixed.

And as the general recommendation is to never ever fiddle with pg_xlog/ contents, I’m not even sure what to do about it.

- D.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2015-01-02 11:42:45 Re: Parallel Seq Scan
Previous Message Amit Kapila 2015-01-02 11:13:54 Re: Parallel Seq Scan