Fix a strict aliasing violation This one is almost a textbook example of an aliasing violation, and it is straightforward to fix, so clean it up. (The warning only shows up if you remove the -fno-strict-aliasing option.) Also, move the code after the error checking. Doesn't make a difference technically, but it seems strange to do actions before errors are checked.
Reported-by: Tatsuo Ishii <[email protected]> Reviewed-by: Tom Lane <[email protected]> Discussion: https://www.postgresql.org/message-id/flat/20240724.155525.366150353176322967.ishii%40postgresql.org Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/2fcc5a715130fbe9fb6eadf338e3bfe560eb0cb5 Modified Files -------------- src/backend/replication/logical/origin.c | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-)
