This makes almost all core code follow the policy introduced in the previous commit. Specific decisions: - Text search support functions with char* and length arguments, such as prsstart and lexize, may receive unaligned strings. I doubt maintainers of non-core text search code will notice. - Use plain VARDATA() on values detoasted or synthesized earlier in the same function. Use VARDATA_ANY() on varlenas sourced outside the function, even if they happen to always have four-byte headers. As an exception, retain the universal practice of using VARDATA() on return values of SendFunctionCall(). - Retain PG_GETARG_BYTEA_P() in pageinspect. (Page images are too large for a one-byte header, so this misses no optimization.) Sites that do not call get_page_from_raw() typically need the four-byte alignment. - For now, do not change btree_gist. Its use of four-byte headers in memory is partly entangled with storage of 4-byte headers inside GBT_VARKEY, on disk. - For now, do not change gtrgm_consistent() or gtrgm_distance(). They incorporate the varlena header into a cache, and there are multiple credible implementation strategies to consider. |
||
---|---|---|
.. | ||
expected | ||
po | ||
sql | ||
.gitignore | ||
GNUmakefile | ||
README | ||
SPI.xs | ||
Util.xs | ||
nls.mk | ||
plc_perlboot.pl | ||
plc_trusted.pl | ||
plperl--1.0.sql | ||
plperl--unpackaged--1.0.sql | ||
plperl.c | ||
plperl.control | ||
plperl.h | ||
plperl_helpers.h | ||
plperl_opmask.pl | ||
plperlu--1.0.sql | ||
plperlu--unpackaged--1.0.sql | ||
plperlu.control | ||
ppport.h | ||
text2macro.pl |
README
src/pl/plperl/README PL/Perl allows you to write PostgreSQL functions and procedures in Perl. To include PL/Perl in the build use './configure --with-perl'. To build from this directory use 'make all; make install'. libperl must have been built as a shared library, which is usually not the case in standard installations. Consult the PostgreSQL User's Guide and the INSTALL file in the top-level directory of the source distribution for more information.