diff options
| author | Tom Lane | 2015-05-24 16:20:23 +0000 |
|---|---|---|
| committer | Tom Lane | 2015-05-24 16:20:23 +0000 |
| commit | 91e79260f636ab4d5a43910b6a38bc75651ad14c (patch) | |
| tree | 10a3d8b52b29ba4529aba393f5371dbd545bdfbb /doc/src/sgml/gist.sgml | |
| parent | 807b9e0dff663c5da875af7907a5106c0ff90673 (diff) | |
Remove no-longer-required function declarations.
Remove a bunch of "extern Datum foo(PG_FUNCTION_ARGS);" declarations that
are no longer needed now that PG_FUNCTION_INFO_V1(foo) provides that.
Some of these were evidently missed in commit e7128e8dbb305059, but others
were cargo-culted in in code added since then. Possibly that can be blamed
in part on the fact that we'd not fixed relevant documentation examples,
which I've now done.
Diffstat (limited to 'doc/src/sgml/gist.sgml')
| -rw-r--r-- | doc/src/sgml/gist.sgml | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/doc/src/sgml/gist.sgml b/doc/src/sgml/gist.sgml index dd5d6f9fea0..2d1a5aa863f 100644 --- a/doc/src/sgml/gist.sgml +++ b/doc/src/sgml/gist.sgml @@ -327,7 +327,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: <programlisting> -Datum my_consistent(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_consistent); Datum @@ -390,7 +389,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: <programlisting> -Datum my_union(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_union); Datum @@ -464,7 +462,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: <programlisting> -Datum my_compress(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_compress); Datum @@ -525,7 +522,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: <programlisting> -Datum my_decompress(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_decompress); Datum @@ -565,7 +561,6 @@ LANGUAGE C STRICT; -- in some cases penalty functions need not be strict And the matching code in the C module could then follow this skeleton: <programlisting> -Datum my_penalty(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_penalty); Datum @@ -614,7 +609,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: <programlisting> -Datum my_picksplit(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_picksplit); Datum @@ -721,7 +715,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: <programlisting> -Datum my_same(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_same); Datum @@ -772,7 +765,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: <programlisting> -Datum my_distance(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_distance); Datum @@ -859,7 +851,6 @@ LANGUAGE C STRICT; The matching code in the C module could then follow this skeleton: <programlisting> -Datum my_fetch(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_fetch); Datum |