Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_stop_backup() v2 incorrectly marked as proretset - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: pg_stop_backup() v2 incorrectly marked as proretset
Date
Msg-id CAJ7c6TN_MHLv9rH3ijMxVnrL=75JN=yXxXwZ6c7=ETCLk7SWBg@mail.gmail.com
Whole thread Raw
In response to Re: pg_stop_backup() v2 incorrectly marked as proretset  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_stop_backup() v2 incorrectly marked as proretset  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
Tree view
Hi Tom.

Yeah, there's plenty of precedent for that coding if you look around.
I've not read the whole patch, but this snippet seems fine to me
if there's also an #undef at the end of the function.

No, there is no #undef. With #undef I don't mind it either.

--
Best regards,
Aleksander Alekseev

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_stop_backup() v2 incorrectly marked as proretset
Next
From: Tom Lane
Date:
Subject: Re: Allow root ownership of client certificate key