[COMMITTERS] pgsql: Run pgindent on range type files, per request from Tom.

Run pgindent on range type files, per request from Tom. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/cdaa45fd4b09c64d634818e52ef7a2191ce40667 Modified Files -- src/backend/catalog/pg_range.c | 44 +- src/backend/commands/typecmds.c |

[COMMITTERS] pgsql: Rerun pgindent with updated typedef list.

Rerun pgindent with updated typedef list. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/1a2586c1d0d458235b3241834f3f755410301c64 Modified Files -- src/backend/commands/typecmds.c|2 +- src/backend/utils/adt/rangetypes.c | 18 ++-- src/to

[COMMITTERS] pgsql: Fix copyright notices, other minor editing in new range-types co

Fix copyright notices, other minor editing in new range-types code. No functional changes in this commit (except I could not resist the temptation to re-word a couple of error messages). This is just manual cleanup after pgindent to make the code look reasonably like other PG code, in preparation

[COMMITTERS] pgsql: Return FALSE instead of throwing error for comparisons with empt

Return FALSE instead of throwing error for comparisons with empty ranges. Change range_before, range_after, range_adjacent to return false rather than throwing an error when one or both input ranges are empty. The original definition is unnecessarily difficult to use, and also can result in undes

[COMMITTERS] pgsql: Return NULL instead of throwing error when desired bound is not

Return NULL instead of throwing error when desired bound is not available. Change range_lower and range_upper to return NULL rather than throwing an error when the input range is empty or the relevant bound is infinite. Per discussion, throwing an error seems likely to be unduly hard to work with

[COMMITTERS] pgsql: Update oidjoins regression test to match git HEAD.

Update oidjoins regression test to match git HEAD. This is mostly to add some sanity checking for the pg_range catalog. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/4165d5b6d7d2e399edbc6d027039358794aa8f04 Modified Files -- src/test/regress/expected/o

[COMMITTERS] pgsql: Fix alignment and toasting bugs in range types.

Fix alignment and toasting bugs in range types. A range type whose element type has 'd' alignment must have 'd' alignment itself, else there is no guarantee that the element value can be used in-place. (Because range_deserialize uses att_align_pointer which forcibly aligns the given pointer, viol