On 2020-Apr-09, Alvaro Herrera wrote: > It seems worth pointing out that the new GetWalRcvWriteRecPtr function > has a different signature from the original one -- so any third-party > code using the original function will now get a compile failure that > should alert them that they need to change their code to call > GetWalRcvFlushRecPtr instead. Maybe we should add a line or two in the > comments GetWalRcvWriteRecPtr to make this explicit.
After using codesearch.debian.net and finding no results, I decided that this is not worth the effort. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
