- 24 8月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
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
-
- 23 8月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 22 8月, 1998 7 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
test isn't that complete up to now, but I think it shows enough of the capabilities of the module. The Makefile assumes it is located in a directory under pgsql/src/pl. Since it includes Makefile.global and Makefile.port and doesn't use any own compiler/linker calls, it should build on most of our supported platforms (I only tested under Linux up to now). It requires flex and bison I think. Maybe we should ship prepared gram.c etc. like for the main parser too? Jan
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
usernames and passwords work correctly in both "password" and "crypt" authorization mode. NOTE: at least on my machine, it seems that the crypt() routines ignore the part of the password beyond 8 characters, so there's no security gain from longer passwords in crypt auth mode. But they don't fail. The login-related part of psql has apparently not been touched since roughly the fall of Rome ;-). It was going through huge pushups to get around the lack of username/login parameters to PQsetdb. I don't know when PQsetdbLogin was added to libpq, but it's there now ... so I was able to rip out quite a lot of crufty code while I was at it. It's possible that there are still bogus length limits on username or password in some of the other PostgreSQL user interfaces besides psql/libpq. I will leave it to other folks to check that code. regards, tom lane
-
由 Bruce Momjian 提交于
with the new support for asynchronous NOTIFY in libpgtcl. With the current sources, if the backend disconnects unexpectedly then the tcl/tk application coredumps when control next reaches the idle loop. Oops. regards, tom lane
-
由 Bruce Momjian 提交于
Here are additional patches for the UnixWare 7 port. Summary of changes: In pqcomm.h, use the SUN_LEN macro if it is defined to calculate the size of the sockaddr_un structure. In unixware.h, drop the use of the UNIXWARE macro. Everything can be handled with the USE_UNIVEL_CC and DISABLE_COMPLEX_MACRO macros. In s_lock.h, remove the reference to the UNIXWARE macro (see above). In the unixware template, add the YFLAGS:-d line. In various makefile templates, add (or cleanup) unixware and univel port specific information. -- Billy G. Allie
-
由 Bruce Momjian 提交于
-
- 21 8月, 1998 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 20 8月, 1998 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 19 8月, 1998 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
no longer returns buffer pointer, can be gotten from scan; descriptor; bootstrap can create multi-key indexes; pg_procname index now is multi-key index; oidint2, oidint4, oidname are gone (must be removed from regression tests); use System Cache rather than sequential scan in many places; heap_modifytuple no longer takes buffer parameter; remove unused buffer parameter in a few other functions; oid8 is not index-able; remove some use of single-character variable names; cleanup Buffer variables usage and scan descriptor looping; cleaned up allocation and freeing of tuples; 18k lines of diff;
-
由 Marc G. Fournier 提交于
Fix for SNPRINTF test in configure From: Tom Lane <tgl@sss.pgh.pa.us>
-
由 Marc G. Fournier 提交于
Add rule tests to regression tests...
-
- 18 8月, 1998 13 次提交
-
-
由 Marc G. Fournier 提交于
From: Jan Wieck <jwieck@debis.com> Hi, as proposed here comes the first patch for the query rewrite system. <for details, see archive dated Mon, 17 Aug 1998>
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
into cleaner html output file names.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
Add a note on sgml-tools that they are now working with jade and so may become the toolset of choice in the future.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
conflicting with the tutorial.sgml container document.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
Instead of directly showing the random results, test the results for the expected behavior (range and randomness).
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
in constraint clauses. IN and NOT IN only allow constaints, not subselects. Jose' Soares' new reference docs pointed out the discrepency. Updating the docs too...
-
由 Thomas G. Lockhart 提交于
in type checking for DEFAULT contraint clauses. Could do more type coersion later...
-
- 17 8月, 1998 4 次提交
-
-
由 Marc G. Fournier 提交于
From: Tom Lane <tgl@sss.pgh.pa.us>To: pgsql-patches@postgreSQL.org Sigh. That tweak needs a tweak --- I didn't realize that ".DEFAULT" processing ignores dependencies, at least in the version of gmake I have here (not sure if it's a bug or not). Apply this patch aftermy previous one...
-
由 Marc G. Fournier 提交于
Just a couple of "after-commit" cleanups...
-
由 Marc G. Fournier 提交于
Date: Sun, 16 Aug 1998 14:56:48 -0400 From: Tom Lane <tgl@sss.pgh.pa.us> Attached is a patch for this weekend's work on libpq. I've dealt with several issues: <for details: see message, in pgsql-patches archive for above data>
-
由 Marc G. Fournier 提交于
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Here is some more contrib-fodder, based on TIH's IP address type, for ISBN and ISSN identifiers (which I just happened to need to keep track of the things in my library).
-
- 16 8月, 1998 2 次提交
-
-
由 Thomas G. Lockhart 提交于
Previously, had thrown an error, but looking for alternate strategies for table indices utilization would prefer to continue.
-
由 Thomas G. Lockhart 提交于
Don't bother checking for alternate strategies if so since it was more likely a function or some other non-operator anyway.
-