On Tue, Jan 19, 2021 at 2:56 PM Corey Huinker <corey.huin...@gmail.com> wrote: >> In file included from >> /home/japin/Codes/postgresql/Debug/../src/include/postgres.h:47:0, >> from >> /home/japin/Codes/postgresql/Debug/../src/backend/utils/adt/ri_triggers.c:24: >> /home/japin/Codes/postgresql/Debug/../src/backend/utils/adt/ri_triggers.c: >> In function ‘ri_PrimaryKeyExists’: >> /home/japin/Codes/postgresql/Debug/../src/include/utils/elog.h:134:5: >> warning: this statement may fall through [-Wimplicit-fallthrough=] >> do { \ >> ^ >> /home/japin/Codes/postgresql/Debug/../src/include/utils/elog.h:156:2: note: >> in expansion of macro ‘ereport_domain’ >> ereport_domain(elevel, TEXTDOMAIN, __VA_ARGS__) >> ^~~~~~~~~~~~~~ >> /home/japin/Codes/postgresql/Debug/../src/include/utils/elog.h:229:2: note: >> in expansion of macro ‘ereport’ >> ereport(elevel, errmsg_internal(__VA_ARGS__)) >> ^~~~~~~ >> /home/japin/Codes/postgresql/Debug/../src/backend/utils/adt/ri_triggers.c:417:5: >> note: in expansion of macro ‘elog’ >> elog(ERROR, "unexpected table_tuple_lock status: %u", res); >> ^~~~ >> /home/japin/Codes/postgresql/Debug/../src/backend/utils/adt/ri_triggers.c:419:4: >> note: here >> default: >> ^~~~~~~
Thanks, will fix it. -- Amit Langote EDB: http://www.enterprisedb.com