Linux server.edchosting.com 4.18.0-553.79.1.lve.el7h.x86_64 #1 SMP Wed Oct 15 16:34:46 UTC 2025 x86_64
LiteSpeed
Server IP : 75.98.162.185 & Your IP : 216.73.216.163
Domains :
Cant Read [ /etc/named.conf ]
User : goons4good
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
include /
pgsql /
server /
nodes /
Delete
Unzip
Name
Size
Permission
Date
Action
bitmapset.h
3.36
KB
-rw-r--r--
2021-06-15 13:00
execnodes.h
64.77
KB
-rw-r--r--
2021-06-15 13:00
makefuncs.h
2.32
KB
-rw-r--r--
2021-06-15 13:00
memnodes.h
2.55
KB
-rw-r--r--
2021-06-15 13:00
nodeFuncs.h
2.45
KB
-rw-r--r--
2021-06-15 13:00
nodes.h
14.35
KB
-rw-r--r--
2021-06-15 13:00
params.h
3.69
KB
-rw-r--r--
2021-06-15 13:00
parsenodes.h
86.96
KB
-rw-r--r--
2021-06-15 13:00
pg_list.h
11.49
KB
-rw-r--r--
2021-06-15 13:00
plannodes.h
27.61
KB
-rw-r--r--
2021-06-15 13:00
primnodes.h
50.04
KB
-rw-r--r--
2021-06-15 13:00
print.h
1.04
KB
-rw-r--r--
2021-06-15 13:00
readfuncs.h
897
B
-rw-r--r--
2021-06-15 13:00
relation.h
68.13
KB
-rw-r--r--
2021-06-15 13:00
replnodes.h
1.03
KB
-rw-r--r--
2021-06-15 13:00
tidbitmap.h
2.19
KB
-rw-r--r--
2021-06-15 13:00
value.h
1.76
KB
-rw-r--r--
2021-06-15 13:00
Save
Rename
/*------------------------------------------------------------------------- * * value.h * interface for Value nodes * * * Copyright (c) 2003-2012, PostgreSQL Global Development Group * * src/include/nodes/value.h * *------------------------------------------------------------------------- */ #ifndef VALUE_H #define VALUE_H #include "nodes/nodes.h" /*---------------------- * Value node * * The same Value struct is used for five node types: T_Integer, * T_Float, T_String, T_BitString, T_Null. * * Integral values are actually represented by a machine integer, * but both floats and strings are represented as strings. * Using T_Float as the node type simply indicates that * the contents of the string look like a valid numeric literal. * * (Before Postgres 7.0, we used a double to represent T_Float, * but that creates loss-of-precision problems when the value is * ultimately destined to be converted to NUMERIC. Since Value nodes * are only used in the parsing process, not for runtime data, it's * better to use the more general representation.) * * Note that an integer-looking string will get lexed as T_Float if * the value is too large to fit in a 'long'. * * Nulls, of course, don't need the value part at all. *---------------------- */ typedef struct Value { NodeTag type; /* tag appropriately (eg. T_String) */ union ValUnion { long ival; /* machine integer */ char *str; /* string */ } val; } Value; #define intVal(v) (((Value *)(v))->val.ival) #define floatVal(v) atof(((Value *)(v))->val.str) #define strVal(v) (((Value *)(v))->val.str) extern Value *makeInteger(long i); extern Value *makeFloat(char *numericStr); extern Value *makeString(char *str); extern Value *makeBitString(char *str); #endif /* VALUE_H */