mirror of
https://github.com/postgres/postgres.git
synced 2025-11-04 20:11:56 +03:00
c7b8998ebb
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4d wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
65 lines
1.9 KiB
C
65 lines
1.9 KiB
C
/*-------------------------------------------------------------------------
|
|
*
|
|
* numeric.h
|
|
* Definitions for the exact numeric data type of Postgres
|
|
*
|
|
* Original coding 1998, Jan Wieck. Heavily revised 2003, Tom Lane.
|
|
*
|
|
* Copyright (c) 1998-2017, PostgreSQL Global Development Group
|
|
*
|
|
* src/include/utils/numeric.h
|
|
*
|
|
*-------------------------------------------------------------------------
|
|
*/
|
|
#ifndef _PG_NUMERIC_H_
|
|
#define _PG_NUMERIC_H_
|
|
|
|
#include "fmgr.h"
|
|
|
|
/*
|
|
* Limit on the precision (and hence scale) specifiable in a NUMERIC typmod.
|
|
* Note that the implementation limit on the length of a numeric value is
|
|
* much larger --- beware of what you use this for!
|
|
*/
|
|
#define NUMERIC_MAX_PRECISION 1000
|
|
|
|
/*
|
|
* Internal limits on the scales chosen for calculation results
|
|
*/
|
|
#define NUMERIC_MAX_DISPLAY_SCALE NUMERIC_MAX_PRECISION
|
|
#define NUMERIC_MIN_DISPLAY_SCALE 0
|
|
|
|
#define NUMERIC_MAX_RESULT_SCALE (NUMERIC_MAX_PRECISION * 2)
|
|
|
|
/*
|
|
* For inherently inexact calculations such as division and square root,
|
|
* we try to get at least this many significant digits; the idea is to
|
|
* deliver a result no worse than float8 would.
|
|
*/
|
|
#define NUMERIC_MIN_SIG_DIGITS 16
|
|
|
|
/* The actual contents of Numeric are private to numeric.c */
|
|
struct NumericData;
|
|
typedef struct NumericData *Numeric;
|
|
|
|
/*
|
|
* fmgr interface macros
|
|
*/
|
|
|
|
#define DatumGetNumeric(X) ((Numeric) PG_DETOAST_DATUM(X))
|
|
#define DatumGetNumericCopy(X) ((Numeric) PG_DETOAST_DATUM_COPY(X))
|
|
#define NumericGetDatum(X) PointerGetDatum(X)
|
|
#define PG_GETARG_NUMERIC(n) DatumGetNumeric(PG_GETARG_DATUM(n))
|
|
#define PG_GETARG_NUMERIC_COPY(n) DatumGetNumericCopy(PG_GETARG_DATUM(n))
|
|
#define PG_RETURN_NUMERIC(x) return NumericGetDatum(x)
|
|
|
|
/*
|
|
* Utility functions in numeric.c
|
|
*/
|
|
extern bool numeric_is_nan(Numeric num);
|
|
int32 numeric_maximum_size(int32 typmod);
|
|
extern char *numeric_out_sci(Numeric num, int scale);
|
|
extern char *numeric_normalize(Numeric num);
|
|
|
|
#endif /* _PG_NUMERIC_H_ */
|