Tom Lane 4bd1994650 Make DatumGetFoo/PG_GETARG_FOO/PG_RETURN_FOO macro names more consistent. ... By project convention, these names should include "P" when dealing with a pointer type; that is, if the result of a GETARG macro is of type FOO *, it should be called PG_GETARG_FOO_P not just PG_GETARG_FOO. Some newer types such as JSONB and ranges had not followed the convention, and a number of contrib modules hadn't gotten that memo either. Rename the offending macros to improve consistency. In passing, fix a few places that thought PG_DETOAST_DATUM() returns a Datum; it does not, it returns "struct varlena *". Applying DatumGetPointer to that happens not to cause any bad effects today, but it's formally wrong. Also, adjust an ltree macro that was designed without any thought for what pgindent would do with it. This is all cosmetic and shouldn't have any impact on generated code. Mark Dilger, some further tweaks by me Discussion: https://postgr.es/m/EA5676F4-766F-4F38-8348-ECC7DB427C6A@gmail.com		2017-09-18 15:21:23 -04:00
..
expected	psql: Use more consistent capitalization of some output headings	2017-06-13 14:41:14 -04:00
sql	Suppress indentation from Data::Dumper in regression tests	2017-05-14 01:10:18 -04:00
.gitignore
hstore_plperl--1.0.sql
hstore_plperl.c	Make DatumGetFoo/PG_GETARG_FOO/PG_RETURN_FOO macro names more consistent.	2017-09-18 15:21:23 -04:00
hstore_plperl.control
hstore_plperlu--1.0.sql
hstore_plperlu.control
Makefile	PL/Perl portability fix: absorb relevant -D switches from Perl.	2017-07-28 14:25:28 -04:00