Make walsender always initialize the buffers.
Walsender uses the local buffers for each outgoing and incoming message.
Previously when creating replication slot, walsender forgot to initialize
one of them and which can cause the segmentation fault error. To fix this
issue, this commit changes wals
Make walsender always initialize the buffers.
Walsender uses the local buffers for each outgoing and incoming message.
Previously when creating replication slot, walsender forgot to initialize
one of them and which can cause the segmentation fault error. To fix this
issue, this commit changes wals
Make walsender always initialize the buffers.
Walsender uses the local buffers for each outgoing and incoming message.
Previously when creating replication slot, walsender forgot to initialize
one of them and which can cause the segmentation fault error. To fix this
issue, this commit changes wals
Make walsender always initialize the buffers.
Walsender uses the local buffers for each outgoing and incoming message.
Previously when creating replication slot, walsender forgot to initialize
one of them and which can cause the segmentation fault error. To fix this
issue, this commit changes wals
Fujii Masao writes:
> Make walsender always initialize the buffers.
> ...
> Back-patch to 9.4 where replication slot was introduced.
Doesn't look like you actually pushed the back-patch? I only see
this in HEAD.
regards, tom lane
--
Sent via pgsql-committers mailing l
On Wed, Feb 22, 2017 at 4:04 AM, Tom Lane wrote:
> Fujii Masao writes:
>> Make walsender always initialize the buffers.
>> ...
>> Back-patch to 9.4 where replication slot was introduced.
>
> Doesn't look like you actually pushed the back-patch? I only see
> this in HEAD.
Oh, sorry... I pushed t
