On Tue, Nov 28, 2017 at 9:10 AM, Harshal Dhumal <
harshal.dhu...@enterprisedb.com> wrote:
> Hi Dave,
> --
> On Mon, Nov 27, 2017 at 9:20 PM, Harshal Dhumal > wrote:
>
>>
>>
>> On Mon, Nov 27, 2017 at 6:32 PM, Dave Page wrote:
>>
>>> Hi
>>>
>>> On Mon, Nov 27, 2017 at 12:29 PM, Harshal Dhumal <
>
Hi Dave,
--
On Mon, Nov 27, 2017 at 9:20 PM, Harshal Dhumal
wrote:
>
>
> On Mon, Nov 27, 2017 at 6:32 PM, Dave Page wrote:
>
>> Hi
>>
>> On Mon, Nov 27, 2017 at 12:29 PM, Harshal Dhumal <
>> harshal.dhu...@enterprisedb.com> wrote:
>>
>>> Hi Dave,
>>>
>>> Please find updated patch.
>>>
>>> --
>>
On Mon, Nov 27, 2017 at 6:32 PM, Dave Page wrote:
> Hi
>
> On Mon, Nov 27, 2017 at 12:29 PM, Harshal Dhumal <
> harshal.dhu...@enterprisedb.com> wrote:
>
>> Hi Dave,
>>
>> Please find updated patch.
>>
>> --
>> *Harshal Dhumal*
>> *Sr. Software Engineer*
>>
>> EnterpriseDB India: http://www.enter
Hi Dave,
Please find updated patch.
--
*Harshal Dhumal*
*Sr. Software Engineer*
EnterpriseDB India: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Mon, Nov 27, 2017 at 5:28 PM, Dave Page wrote:
> Hi
>
> On Mon, Nov 27, 2017 at 11:23 AM, Harshal Dhumal <
> harshal.dhu...@ent
Hi
On Mon, Nov 27, 2017 at 11:23 AM, Harshal Dhumal <
harshal.dhu...@enterprisedb.com> wrote:
> Hi,
>
> Please find attached patch to fix RM2811
>
> Issue was caused due to assumption made when current position in log file
> while reading it reaches to last line then
> we were assuming process is