mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-17 04:01:09 +02:00
611806cd72
Since C99, there can be a trailing comma after the last value in an enum definition. A lot of new code has been introducing this style on the fly. Some new patches are now taking an inconsistent approach to this. Some add the last comma on the fly if they add a new last value, some are trying to preserve the existing style in each place, some are even dropping the last comma if there was one. We could nudge this all in a consistent direction if we just add the trailing commas everywhere once. I omitted a few places where there was a fixed "last" value that will always stay last. I also skipped the header files of libpq and ecpg, in case people want to use those with older compilers. There were also a small number of cases where the enum type wasn't used anywhere (but the enum values were), which ended up confusing pgindent a bit, so I left those alone. Discussion: https://www.postgresql.org/message-id/flat/386f8c45-c8ac-4681-8add-e3b0852c1620%40eisentraut.org
42 lines
540 B
C
42 lines
540 B
C
/*
|
|
* contrib/btree_gist/btree_gist.h
|
|
*/
|
|
#ifndef __BTREE_GIST_H__
|
|
#define __BTREE_GIST_H__
|
|
|
|
#include "access/nbtree.h"
|
|
#include "fmgr.h"
|
|
|
|
#define BtreeGistNotEqualStrategyNumber 6
|
|
|
|
/* indexed types */
|
|
|
|
enum gbtree_type
|
|
{
|
|
gbt_t_var,
|
|
gbt_t_int2,
|
|
gbt_t_int4,
|
|
gbt_t_int8,
|
|
gbt_t_float4,
|
|
gbt_t_float8,
|
|
gbt_t_numeric,
|
|
gbt_t_ts,
|
|
gbt_t_cash,
|
|
gbt_t_oid,
|
|
gbt_t_time,
|
|
gbt_t_date,
|
|
gbt_t_intv,
|
|
gbt_t_macad,
|
|
gbt_t_macad8,
|
|
gbt_t_text,
|
|
gbt_t_bpchar,
|
|
gbt_t_bytea,
|
|
gbt_t_bit,
|
|
gbt_t_bool,
|
|
gbt_t_inet,
|
|
gbt_t_uuid,
|
|
gbt_t_enum,
|
|
};
|
|
|
|
#endif
|