database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-26 12:21:12 +03:00
Code Activity

Remove no-longer-required function declarations.

Browse Source 
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 e7128e8dbb, 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.
This commit is contained in:
Tom Lane
2015-05-24 12:20:23 -04:00
parent 807b9e0dff
commit 91e79260f6
37 changed files with 3 additions and 170 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/gist.sgml
View File

@ -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