Re: [HACKERS] Reversed sync check in pg_receivewal - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: [HACKERS] Reversed sync check in pg_receivewal
Date
Msg-id CABUevExMz0xmhmVKU8ZU-J8OUUOVGGZ8X-G8UXBK2NOuj+-2kQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Reversed sync check in pg_receivewal  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Reversed sync check in pg_receivewal  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Apr 11, 2017 at 3:19 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writes:
> Attached patch reverses the check, and adds a failure message. I'd
> appreciate a quick review in case I have the logic backwards in my head...

I think the patch is correct, but if there's any documentation of the
walmethod APIs that would allow one to assert which side of the API got
this wrong, I sure don't see it.  Would it be unreasonable to insist
on some documentation around that?


Agreed.

Would you say comments in the struct in walmethods.h is enough, or were you thinking actual sgml docs when you commented that? 


--

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: [HACKERS] Reversed sync check in pg_receivewal
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)