</para>

<para>

MostPostgres developers don't need to be directly concerned with

MostPostgreSQL developers don't need to be directly concerned with

the <acronym>BKI</acronym> file, but almost any nontrivial feature

addition in the backend will require modifying the catalog header files

and/or initial data files. The rest of this chapter gives some

of <literal>DYLD_LIBRARY_PATH</literal> down to the executables being

tested. You can work around that by doing <literal>make

install</literal> before <literal>make check</literal>.

MostPostgres developers just turn off SIP, though.

MostPostgreSQL developers just turn off SIP, though.

</para>

</sect2>