- 10 12月, 2000 2 次提交
- 09 12月, 2000 5 次提交
-
-
由 Tatsuo Ishii 提交于
Thanks Chih-Chang Hsieh <cch@cc.kmu.edu.tw> for finding the bug.
-
由 Tom Lane 提交于
varlena type. (I did not force initdb, but you won't see the fix unless you do one.) Also, make sure all index support operators and functions are careful not to leak memory for toasted inputs; I had missed some hash and rtree support ops on this point before.
-
由 Tom Lane 提交于
mostly just on the WAL logfile nowadays. But if people want to disable fsync for performance, why should we say no?
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
value greater than one. The behavior this sought to disallow doesn't seem any less confusing than the other behaviors of cached sequences. Improve wording of some error messages, too. Update documentation accordingly. Also add an explanation that aborted transactions do not roll back their nextval() calls; this seems to be a FAQ, so it ought to be mentioned here...
-
- 08 12月, 2000 5 次提交
-
-
由 Hiroshi Inoue 提交于
-
由 Hiroshi Inoue 提交于
-
由 Tom Lane 提交于
length is less than original string length.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
As I read it, the spec requires a non-null result in some cases where one of the inputs is NULL: specifically, if the other endpoint of that interval is between the endpoints of the other interval, then the result is known TRUE despite the missing endpoint. The spec could've been a lot simpler if they did not intend this behavior. I did not force an initdb for this change, but if you don't do one you'll still see the old strict-function behavior.
-
- 07 12月, 2000 7 次提交
-
-
由 Hiroshi Inoue 提交于
if the transaction has already been committed ?
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
transformForUpdate does: it should recurse into subqueries.
-
由 Tom Lane 提交于
It could be recursing into a sub-query where there was already a FOR UPDATE clause.
-
由 Tom Lane 提交于
work where we can (given that the executor only handles it at top level) and generate an error where we can't. Note that while the parser has been allowing views to say SELECT FOR UPDATE for a few weeks now, that hasn't actually worked until just now.
-
由 Tom Lane 提交于
the installed header file set.
-
- 06 12月, 2000 4 次提交
-
-
由 Tom Lane 提交于
an error at end of transaction ... and I did *not* like it. Reduce ERROR to NOTICE so that this situation doesn't cause an infinite loop.
-
由 Tom Lane 提交于
an error as we used to. In an OUTER JOIN scenario, retrieving a null CTID from one of the input relations is entirely expected. We still want to lock the input rows from the other relations, so just ignore the null and keep going.
-
由 Tom Lane 提交于
I believe this should fix the issue that Philip Warner noticed about the check for unique constraints meeting the referenced keys of a foreign key constraint allowing the specification of a subset of a foreign key instead of rejecting it. I also added tests for a base case of this to the foreign key and alter table tests and patches for expected output.
-
由 Tom Lane 提交于
report from Joel Burton. Turns out that my simple idea of turning the SELECT into a subquery does not interact well *at all* with the way the rule rewriter works. Really what we need to make INSERT ... SELECT work cleanly is to decouple targetlists from rangetables: an INSERT ... SELECT wants to have two levels of targetlist but only one rangetable. No time for that for 7.1, however, so I've inserted some ugly hacks to make the rewriter know explicitly about the structure of INSERT ... SELECT queries. Ugh :-(
-
- 04 12月, 2000 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
values, whether the local char type is signed or not. This is necessary for portability. Per discussion on pghackers around 9/16/00.
-
由 Tom Lane 提交于
very unhappy ...
-
- 03 12月, 2000 5 次提交
-
-
由 Thomas G. Lockhart 提交于
Allow some operator-like tokens to be used as function names. Flesh out support for time, timetz, and interval operators and interactions. Regression tests pass, but non-reference-platform horology test results will need to be updated.
-
由 Peter Eisentraut 提交于
-
由 Vadim B. Mikheev 提交于
critical sections of code.
-
由 Tom Lane 提交于
COPY BINARY is still broken for toasted data, however.
-
由 Tom Lane 提交于
a toasted datum in VACUUM ANALYZE.
-
- 02 12月, 2000 3 次提交
-
-
由 Tom Lane 提交于
leak memory when printing a toasted attribute, and printtup_internal didn't work at all...
-
由 Tom Lane 提交于
since those routines may do palloc's. We want to be fairly sure we can send the error message to the client even under low-memory conditions. That's what we stashed away 8K in ErrorContext for, after all ...
-
由 Tom Lane 提交于
not-very-good handling of mid-size allocation requests. Do everything via either the "small" case (chunk size rounded up to power of 2) or the "large" case (pass it straight off to malloc()). Increase the number of freelists a little to set the breakpoint between these behaviors at 8K.
-
- 01 12月, 2000 6 次提交
-
-
由 Tom Lane 提交于
immediately uncovered three of Karel's own bugs, including a routine that scribbled on its input (naughty naughty!)
-
由 Tom Lane 提交于
apply Karel Zak's patch to recycle residual space in an exhausted allocation block. (Bet you thought I'd forgot about that, Karel?)
-
由 Tom Lane 提交于
I hope all the dust has settled out now ...
-
由 Peter Eisentraut 提交于
$(CC) $(CFLAGS) $(LDFLAGS) <object files> <extra-libraries> $(LIBS) -o $@ This form seemed to be the most portable, readable, and logical, but in any case it's better than having a dozen different ones in the tree.
-
由 Vadim B. Mikheev 提交于
-
由 Vadim B. Mikheev 提交于
-