On Tue, Apr 11, 2017 at 4:50 PM, Masahiko Sawada wrote:
> On Tue, Apr 11, 2017 at 1:39 AM, Fujii Masao wrote:
>> On Mon, Apr 10, 2017 at 9:39 PM, Masahiko Sawada
>> wrote:
>>> On Mon, Apr 10, 2017 at 9:32 PM, Petr Jelinek
>>> wrote:
On 10/04/17 07:16, Masahiko Sawada wrote:
> Hi all,
On Tue, Apr 11, 2017 at 1:39 AM, Fujii Masao wrote:
> On Mon, Apr 10, 2017 at 9:39 PM, Masahiko Sawada
> wrote:
>> On Mon, Apr 10, 2017 at 9:32 PM, Petr Jelinek
>> wrote:
>>> On 10/04/17 07:16, Masahiko Sawada wrote:
Hi all,
Attached a patch for $subject.
I added this p
On Mon, Apr 10, 2017 at 9:39 PM, Masahiko Sawada wrote:
> On Mon, Apr 10, 2017 at 9:32 PM, Petr Jelinek
> wrote:
>> On 10/04/17 07:16, Masahiko Sawada wrote:
>>> Hi all,
>>>
>>> Attached a patch for $subject.
>>>
>>> I added this parameter into "Asynchronous Behavior" section of
>>> "RESOURCE" se
On Mon, Apr 10, 2017 at 9:32 PM, Petr Jelinek
wrote:
> On 10/04/17 07:16, Masahiko Sawada wrote:
>> Hi all,
>>
>> Attached a patch for $subject.
>>
>> I added this parameter into "Asynchronous Behavior" section of
>> "RESOURCE" section. But GUC parameter for subscriber now is written in
>> this se
On 10/04/17 07:16, Masahiko Sawada wrote:
> Hi all,
>
> Attached a patch for $subject.
>
> I added this parameter into "Asynchronous Behavior" section of
> "RESOURCE" section. But GUC parameter for subscriber now is written in
> this section, in spite of there is "REPLICATION" section. I think th
Hi all,
Attached a patch for $subject.
I added this parameter into "Asynchronous Behavior" section of
"RESOURCE" section. But GUC parameter for subscriber now is written in
this section, in spite of there is "REPLICATION" section. I think that
we can coordinate these parameters to not confuse use
