- 09 12月, 2000 5 次提交
-
-
由 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?
-
由 Bruce Momjian 提交于
-
由 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 10 次提交
-
-
由 Hiroshi Inoue 提交于
-
由 Hiroshi Inoue 提交于
-
由 Tom Lane 提交于
or return type.
-
由 Tom Lane 提交于
or return type.
-
由 Tom Lane 提交于
or return type.
-
由 Tom Lane 提交于
length is less than original string length.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 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 9 次提交
-
-
由 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.
-
由 Marc G. Fournier 提交于
update VERSION to 7.1beta1..
-
由 Peter Eisentraut 提交于
through to here yet.
-
由 Tom Lane 提交于
the installed header file set.
-
- 06 12月, 2000 5 次提交
-
-
由 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 提交于
-
由 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 9 次提交
-
-
由 Tom Lane 提交于
about being given accurate references to referenced libraries ...
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
directories too, not only src and doc.
-
由 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 提交于
correct on the relevant platforms.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
very unhappy ...
-
- 03 12月, 2000 2 次提交
-
-
由 Peter Eisentraut 提交于
-
由 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.
-