On 03.04.2013 22:50, Jeff Janes wrote:
On Wed, Apr 3, 2013 at 11:14 AM, Heikki Linnakangas
wrote:
On 03.04.2013 18:58, Jeff Janes wrote:
On Tue, Apr 2, 2013 at 10:08 PM, Jeff Janes wrote:
This commit introduced a problem with wal_keep_segments:
commit dfda6ebaec6763090fb78b458a979b**5
On Wed, Apr 3, 2013 at 11:14 AM, Heikki Linnakangas wrote:
> On 03.04.2013 18:58, Jeff Janes wrote:
>
>> On Tue, Apr 2, 2013 at 10:08 PM, Jeff Janes wrote:
>>
>> This commit introduced a problem with wal_keep_segments:
>>>
>>> commit dfda6ebaec6763090fb78b458a979b**558c50b39b
>>>
>>
>> The prob
On 03.04.2013 18:58, Jeff Janes wrote:
On Tue, Apr 2, 2013 at 10:08 PM, Jeff Janes wrote:
This commit introduced a problem with wal_keep_segments:
commit dfda6ebaec6763090fb78b458a979b558c50b39b
The problem seems to be that the underflow warned about is happening,
because the check to guard
On Tue, Apr 2, 2013 at 10:08 PM, Jeff Janes wrote:
> This commit introduced a problem with wal_keep_segments:
>
> commit dfda6ebaec6763090fb78b458a979b558c50b39b
>
The problem seems to be that the underflow warned about is happening,
because the check to guard it was checking the wrong thing.
This commit introduced a problem with wal_keep_segments:
commit dfda6ebaec6763090fb78b458a979b558c50b39b
Author: Heikki Linnakangas
Date: Sun Jun 24 18:06:38 2012 +0300
Don't waste the last segment of each 4GB logical log file.
in a side window do: watch "ls -lrt /tmp/data/pg_xlog"
dfda