|
129 | 129 | </para>
|
130 | 130 |
|
131 | 131 | <para>
|
132 |
| - Frontend code should not include any <structname>pg_xxx.h</structname> |
| 132 | + Frontend code should not include any <filename>pg_xxx.h</filename> |
133 | 133 | catalog header file, as these files may contain C code that won't compile
|
134 | 134 | outside the backend. (Typically, that happens because these files also
|
135 | 135 | contain declarations for functions
|
136 | 136 | in <filename>src/backend/catalog/</filename> files.)
|
137 | 137 | Instead, frontend code may include the corresponding
|
138 |
| - generated <structname>pg_xxx_d.h</structname> header, which will contain |
| 138 | + generated <filename>pg_xxx_d.h</filename> header, which will contain |
139 | 139 | OID <literal>#define</literal>s and any other data that might be of use
|
140 | 140 | on the client side. If you want macros or other code in a catalog header
|
141 | 141 | to be visible to frontend code, write <literal>#ifdef
|
142 | 142 | EXPOSE_TO_CLIENT_CODE</literal> ... <literal>#endif</literal> around that
|
143 | 143 | section to instruct <filename>genbki.pl</filename> to copy that section
|
144 |
| - to the <structname>pg_xxx_d.h</structname> header. |
| 144 | + to the <filename>pg_xxx_d.h</filename> header. |
145 | 145 | </para>
|
146 | 146 |
|
147 | 147 | <para>
|
|
419 | 419 | Use of symbolic references is enabled in a particular catalog column
|
420 | 420 | by attaching <literal>BKI_LOOKUP(<replaceable>lookuprule</replaceable>)</literal>
|
421 | 421 | to the column's definition, where <replaceable>lookuprule</replaceable>
|
422 |
| - is <structname>pg_am</structname>, <structname>pg_proc</structname>, |
423 |
| - <structname>pg_operator</structname>, |
424 |
| - <structname>pg_opclass</structname>, |
425 |
| - <structname>pg_opfamily</structname>, |
426 |
| - or <structname>pg_type</structname>. |
| 422 | + is <literal>pg_am</literal>, <literal>pg_proc</literal>, |
| 423 | + <literal>pg_operator</literal>, <literal>pg_opclass</literal>, |
| 424 | + <literal>pg_opfamily</literal>, or <literal>pg_type</literal>. |
427 | 425 | <literal>BKI_LOOKUP</literal> can be attached to columns of
|
428 | 426 | type <type>Oid</type>, <type>regproc</type>, <type>oidvector</type>,
|
429 | 427 | or <type>Oid[]</type>; in the latter two cases it implies performing a
|
|
0 commit comments