- 19 9月, 2002 5 次提交
-
-
由 Tom Lane 提交于
to be flexible about assignment casts without introducing ambiguity in operator/function resolution. Introduce a well-defined promotion hierarchy for numeric datatypes (int2->int4->int8->numeric->float4->float8). Change make_const to initially label numeric literals as int4, int8, or numeric (never float8 anymore). Explicitly mark Func and RelabelType nodes to indicate whether they came from a function call, explicit cast, or implicit cast; use this to do reverse-listing more accurately and without so many heuristics. Explicit casts to char, varchar, bit, varbit will truncate or pad without raising an error (the pre-7.2 behavior), while assigning to a column without any explicit cast will still raise an error for wrong-length data like 7.3. This more nearly follows the SQL spec than 7.2 behavior (we should be reporting a 'completion condition' in the explicit-cast cases, but we have no mechanism for that, so just do silent truncation). Fix some problems with enforcement of typmod for array elements; it didn't work at all in 'UPDATE ... SET array[n] = foo', for example. Provide a generalized array_length_coerce() function to replace the specialized per-array-type functions that used to be needed (and were missing for NUMERIC as well as all the datetime types). Add missing conversions int8<->float4, text<->numeric, oid<->int8. initdb forced.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
Also, some editing in PL/Perl and PL/Python chapters.
-
由 Peter Eisentraut 提交于
-
- 18 9月, 2002 9 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tatsuo Ishii 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> o Allow EXPLAIN EXECUTE to see prepared plans
-
由 Tatsuo Ishii 提交于
-
由 Tatsuo Ishii 提交于
conversion function interface.
-
由 Bruce Momjian 提交于
> * Allow pg_xlog to be moved without symlinks
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 17 9月, 2002 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
- 16 9月, 2002 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
(notify/SI-overrun interrupt) while it is in process of doing proc_exit, it is possible for Async_NotifyHandler() to try to start a transaction when one is already running. This leads to Asserts() or worse. I think it may only be possible to occur when frontend synchronization is lost (ie, the elog(FATAL) in SocketBackend() fires), but that is a standard occurrence after error during COPY. In any case, I have seen this failure occur during regression tests, so it is definitely possible.
-
- 15 9月, 2002 12 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
non-standard regression test, and adds standard installcheck regression test support. The test creates a second database (regression_slave) and drops it again, in order to avoid the cheesy-ness of connecting back to the same database ;-) Joe Conway
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Joe Conway
-
由 Tom Lane 提交于
contrib/tablefunc. Specifically it replaces the use of VIEWs (for needed composite type creation) with use of CREATE TYPE. It also performs GRANT EXECUTE ON FUNCTION foo() TO PUBLIC for all of the created functions. There was also a cosmetic change to two regression files. Joe Conway
-
由 Tom Lane 提交于
Kenji Sugita.
-
由 Tom Lane 提交于
Also try to improve readability and performance.
-
由 Peter Eisentraut 提交于
inline documentation to the main docs.
-
- 14 9月, 2002 2 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Barry Lind 提交于
and fixed a bug found by the regression test Modified Files: jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java jdbc/org/postgresql/test/jdbc2/Jdbc2TestSuite.java Added Files: jdbc/org/postgresql/test/jdbc2/ServerPreparedStmtTest.java
-
- 13 9月, 2002 3 次提交
-
-
由 Tatsuo Ishii 提交于
Change PG_RETURN_INT32(0) to PG_RETURN_VOID()
-
由 Peter Eisentraut 提交于
material into the new location.
-
由 Tom Lane 提交于
don't assume relname field of a relcache entry will stay valid across lots of operations.
-
- 12 9月, 2002 2 次提交
-
-
由 Tom Lane 提交于
doesn't match any known variable.
-
由 Bruce Momjian 提交于
fmgr.h - it's discouraged to access fcinfo directly but there is no macro to get the number of arguments passed to the function. Checking the number of arguments is often useful when you have a function which can be called like: func('arg'); func(null); func(); all mapping to the same C function. the macro has a function-like appearance to match the other PG_* macros. Lee Kindness.
-