- 22 5月, 1999 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Thomas G. Lockhart 提交于
and the integrated doc. Clean up other markup.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Michael Meskes 提交于
-
- 21 5月, 1999 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tatsuo Ishii 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
update material about client connection failure messages.
-
由 Tom Lane 提交于
failure messages.
-
由 Tom Lane 提交于
clauses in CREATE OPERATOR. Needs markup work.
-
由 Tom Lane 提交于
-
由 Jan Wieck 提交于
from initdb again. Added two new commands, createlang and destroylang to bin. These hopefully end this damned mklang.sql discussion. Jan
-
- 20 5月, 1999 14 次提交
-
-
由 Tom Lane 提交于
and trigger function found but returns wrong type.
-
由 Jan Wieck 提交于
SelectStmt and CursorStmt tried to parse FOR UPDATE ... / FOR READ ONLY. Cursor now checks that it is read only by looking at forUpdate of Query. SelectStmt handles FOR READ ONLY too. Jan
-
由 Tatsuo Ishii 提交于
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
Add reference pages for utilities and remove standalone chapters for same. Add material for an appendix on date/time properties, but not yet integrated with the User's Guide. Break up the former chapter on pg_options into Admin and Programmer's Guides.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
INTERNAL functions, add a warning about trying to overload function names for dynamically loaded C functions (from old man page).
-
由 Tom Lane 提交于
many moons ago, but forgot to put here.
-
由 Tom Lane 提交于
entries (prosrc is now name of C-level function).
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 19 5月, 1999 7 次提交
-
-
由 Marc G. Fournier 提交于
Bring python up to date ... From: D'Arcy J.M. Cain <darcy@druid.net>
-
由 Tom Lane 提交于
will pass through rather than spitting up. This is necessary to handle cases where coerce_type causes a subexpression to be retransformed, as in SELECT count(*) + 1.0 FROM table
-
由 Peter Mount 提交于
-
由 Peter Mount 提交于
-
由 Tom Lane 提交于
remove optimizer's arbitrary limit on how large a join it will use hashing for. (The limit was too large to prevent the problems we'd been seeing, anyway...)
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
fixed-size hashtable. This should prevent 'hashtable out of memory' errors, unless you really do run out of memory. Note: target size for hashtable is now taken from -S postmaster switch, not -B, since it is local memory in the backend rather than shared memory.
-
- 18 5月, 1999 5 次提交
-
-
由 Peter Mount 提交于
-
由 Michael Meskes 提交于
-
由 Peter Mount 提交于
-
由 Peter Mount 提交于
-
由 Bruce Momjian 提交于
ALTER TABLE RENAME with extents. Ole Gjerde
-