On Thu, Aug 25, 2011 at 10:16 AM, Heikki Linnakangas
wrote:
> On 25.08.2011 19:11, Robert Haas wrote:
>>
>> On Mon, Aug 22, 2011 at 2:57 AM, Heikki Linnakangas
>> wrote:
>>>
>>> So the problem is that walreceiver merrily writes so much future WAL that
>>> it
>>> runs out of disk space? A limit o
On 25.08.2011 19:11, Robert Haas wrote:
On Mon, Aug 22, 2011 at 2:57 AM, Heikki Linnakangas
wrote:
So the problem is that walreceiver merrily writes so much future WAL that it
runs out of disk space? A limit on the maximum number of future WAL files to
stream ahead would fix that, but I can't
On Mon, Aug 22, 2011 at 2:57 AM, Heikki Linnakangas
wrote:
> So the problem is that walreceiver merrily writes so much future WAL that it
> runs out of disk space? A limit on the maximum number of future WAL files to
> stream ahead would fix that, but I can't get very excited about it. Usually
> y
On 20.08.2011 03:39, Daniel Farina wrote:
The following bug has been logged online:
Bug reference: 6170
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.0.4
Operating system: GNU/Linux Ubuntu 10.04 x86_64
Description:hot standby wedgin
The following bug has been logged online:
Bug reference: 6170
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.0.4
Operating system: GNU/Linux Ubuntu 10.04 x86_64
Description:hot standby wedging on full-WAL disk
Details:
After seeing t
