Hi, On October 7, 2021 8:49:57 AM PDT, Tom Lane >I'm also kind of unclear on why we need to do anything about this >in the community version. If someone has forked PG and changed >APIs to the extent that extensions are unlikely to work, there's >not much stopping them from also making the two-line change >to fmgr.h that would be needed to guarantee that different magic >struct contents are needed.
I can see two reasons. First, it'd probably allow stock pg to generate a better error message when confronted with such a module. Second, there's some value in signaling forks that they should change (or think about changing), that field. Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
