- 16 9月, 1999 3 次提交
-
-
由 Peter Mount 提交于
-
由 Peter Mount 提交于
into it.
-
由 Peter Mount 提交于
to version 2, and fixes ResultSetMetaData.getColumnDisplaySize().
-
- 15 9月, 1999 3 次提交
-
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 Peter Mount 提交于
commit to CVS.
-
- 14 9月, 1999 4 次提交
-
-
由 Thomas G. Lockhart 提交于
for v6.5.2 info.
-
由 Thomas G. Lockhart 提交于
which do not need to be so for our parser. Apparently omitted earlier.
-
由 Peter Mount 提交于
-
由 Bruce Momjian 提交于
-
- 13 9月, 1999 7 次提交
-
-
由 Thomas G. Lockhart 提交于
Almost worked before, but forgot one place to check. Reported by Tatsuo Ishii. Still does not do the right thing if inserting into a non-string target column. Should look for a type coersion later, but doesn't.
-
由 Tom Lane 提交于
message under a kernel that only returns one packet per recv() call. This didn't use to matter much, but it starts to get annoying with multi-megabyte EXPLAIN VERBOSE responses...
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
conditions. There are some pretty bogus heuristics in prepqual.c that try to decide whether to output CNF or DNF format; they need to be replaced, likely. Right now the code is probably too willing to choose DNF form, which might hurt performance in some cases that used to work OK. But at least we have a foundation to build on.
-
由 Marc G. Fournier 提交于
Make sure both SRCH_INC and SRCH_LIB are checked for existances and added to the CPPFLAGS/LDFLAGS variables...
-
由 Marc G. Fournier 提交于
cygwin doesn't have an endian.h, but defines BYTE_ORDER in sys/param.h
-
由 Tom Lane 提交于
in or_normalize, remove detection of duplicate subexpressions (since it's highly unlikely to be worth the amount of time it takes), and introduce a dnfify() entry point so that unintelligible backwards logic in UNION processing can be eliminated. This is just an intermediate step --- next thing is to look at not forcing the qual into CNF form when it would be better off in DNF form.
-
- 12 9月, 1999 4 次提交
-
-
由 Tom Lane 提交于
and pg_server_to_client. Eliminate copy.c's restriction on the length of a single attribute.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
arbitrarily long strings, and frontends should cope gracefully. Goes along with long query and long error message changes...
-
由 Tom Lane 提交于
This change seems necessary in conjunction with long queries, and it cleans up some bogosity in connection with long EXPLAIN texts anyway. Note that current libpq will accept any length error message (at least until it runs out of memory); prior versions have a limit of 8K, but will cleanly discard excess error text, so there shouldn't be any big compatibility problems with old clients.
-
- 10 9月, 1999 3 次提交
-
-
由 Thomas G. Lockhart 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
transaction abort --- before it only worked if there was exactly one level of allocation context stacked in the blank portal. Now it does the right thing for any depth, including zero...
-
- 09 9月, 1999 5 次提交
-
-
由 Tom Lane 提交于
expired messages before concluding that we really have buffer overflow.
-
由 Tom Lane 提交于
cluttering the log file...
-
由 Tom Lane 提交于
was rejecting negative attnums as bogus, which of course they are not. Add code to get_attdisbursion to produce a useful value for OID attribute, since VACUUM does not store stats for system attributes. Also, repair bug that's been in eqjoinsel for a long time: it was taking the max of the two columns' disbursions, whereas it should use the min.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
don't read man pages...
-
- 08 9月, 1999 2 次提交
- 07 9月, 1999 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
space consumption in pull_args, and avoid doing the full CNF transform on operands of operator clauses, where it's really not particularly helpful. This answers the TODO item about large numbers of OR clauses, at least partially. I was able to do a ten-thousand-OR-clause query with about 20Mb memory consumption ... it took an obscenely long time, but it worked...
-
由 Tom Lane 提交于
corrects flex myinput() routine so that it doesn't assume there is only one bufferload of data. We still have the issue of getting rid of YY_USES_REJECT so that the scanner can cope with tokens larger than its initial buffer size.
-
由 Tom Lane 提交于
psql.c seems clean of query length restrictions now.
-
由 Tom Lane 提交于
before comparison; if fields being joined are different widths then hashing will yield wrong answer. Also, remove hashjoinable mark from all uses of array_eq, because array structures may have padding bytes between elements and the pad bytes are of uncertain content. This could be revisited if array code is cleaned up. Modify opr_sanity regress test to complain if array_eq operator is marked hashjoinable.
-
由 Tom Lane 提交于
offended my aesthestic sensibility that there was so much unreadable code doing so little. Rewritten code is about half the size, faster, and (I hope) much more intelligible.
-
由 Tom Lane 提交于
current transaction) are not flushed by shared-cache-inval reset message. SI reset actually works now, for probably the first time in a long time. I was able to run initdb and regression tests with a 16-element SI message array, with a lot of NOTICE: cache state reset messages but no crashes.
-
由 Tom Lane 提交于
system tables, but actually there are only 6 --- see RelationInitialize. Kinda makes you wonder how long ago this code was last executed...
-
- 06 9月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-