aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/dbcommands.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>1998-08-23 22:25:54 +0000
committerBruce Momjian <bruce@momjian.us>1998-08-23 22:25:54 +0000
commit07ae591c87ad256a5c9b081a3eb14ba5549d273f (patch)
treeb59cc37ca712b4fe248db0484e4641870dd0a18b /src/backend/commands/dbcommands.c
parent9cad9febb172b09ff8c2366a4e19469926304f0d (diff)
downloadpostgresql-07ae591c87ad256a5c9b081a3eb14ba5549d273f.tar.gz
postgresql-07ae591c87ad256a5c9b081a3eb14ba5549d273f.zip
Attached is a patch that uses autoconf to determine whether there
is a working 64-bit-int type available. In playing around with it on my machine, I found that gcc provides perfectly fine support for "long long" arithmetic ... but sprintf() and sscanf(), which are system-supplied, don't work :-(. So the autoconf test program does a cursory test on them too. If we find that a lot of systems are like this, it might be worth the trouble to implement binary<->ASCII conversion of int64 ourselves rather than relying on sprintf/sscanf to handle the data type. regards, tom lane
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions