Re: [HACKERS] Bug in Physical Replication Slots (at least 9.5)?

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: nag1010(at)gmail(dot)com, horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp, jdnelson(at)dyn(dot)com, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [HACKERS] Bug in Physical Replication Slots (at least 9.5)?
Date: 2017-03-30 00:41:30
Message-ID: CAB7nPqSfXcptn-V-KGvh1GShRF42Tdv9Nfdjcr1NdH8h1rxJVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Thu, Mar 30, 2017 at 9:12 AM, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
> Committers will not apply patches which has trailing whitespace
> issues. So the patch submitter needs to fix them anyway.

I cannot comment on that point (committers are free to pick up things
the way they want), but just using git commands to apply a patch
should not be an obstacle for a review if a patch can be easily
applied as long as they roughly respect GNU's diff format.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tatsuo Ishii 2017-03-30 00:51:47 Re: [BUGS] Bug in Physical Replication Slots (at least 9.5)?
Previous Message Venkata B Nagothi 2017-03-30 00:12:56 Re: [HACKERS] Bug in Physical Replication Slots (at least 9.5)?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2017-03-30 00:51:47 Re: [BUGS] Bug in Physical Replication Slots (at least 9.5)?
Previous Message Venkata B Nagothi 2017-03-30 00:12:56 Re: [HACKERS] Bug in Physical Replication Slots (at least 9.5)?