- 30 5月, 2000 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 29 5月, 2000 10 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
the src/include tree, so that -I backend is no longer necessary anywhere. Also, clean up some bit rot in contrib tree.
-
由 Tom Lane 提交于
CurrentTriggerData is history.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
pg_language entries.
-
由 Tom Lane 提交于
that have at least one constant-NULL input, even if other inputs are not constants.
-
由 Tom Lane 提交于
Need to update user docs still ...
-
由 Tom Lane 提交于
key call sites are changed, but most called functions are still oldstyle. An exception is that the PL managers are updated (so, for example, NULL handling now behaves as expected in plperl and plpgsql functions). NOTE initdb is forced due to added column in pg_proc.
-
- 28 5月, 2000 1 次提交
-
-
由 Tom Lane 提交于
-
- 27 5月, 2000 11 次提交
-
-
由 Tom Lane 提交于
necessary to call isatty() for each and every received query. That's one less kernel call per query cycle ...
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Most (nearly all) of the work was done by David Wragg <dpw@doc.ic.ac.uk> He patched 6.5.3. I've updated it for 7.0RC5. It works for MIT kerberos 1.1.1 (and previously for 1.0.6 as well). I've got the patch against 6.5.3, plus kerberized RPMS. Mike Wyer <mw@doc.ic.ac.uk> || "Woof?"
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
other than the most common value in a column. We had had 0.5, make it 0.1 to make it more likely that an indexscan will be chosen. Really need better statistics instead, but this should stem the bleeding meanwhile ...
-
- 26 5月, 2000 15 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tatsuo Ishii 提交于
-
由 Tom Lane 提交于
to an undecorated relation name (cf. example from Ed Loehr, 5/25/00).
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
since-closed file descriptors...
-
由 Tom Lane 提交于
subsequent I/O attempts fail cleanly. I'm speculating about failure scenarios in which we do pq_close, then something in a proc_exit routine opens a file (re-using that kernel FD number), then something else fails and tries to write an elog message to the frontend ... message ends up in opened file, oops. No known examples of this but it seems like a potential hole.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
the oper field should be a valid Node structure so it can be dumped by outfuncs.c without risk of coredump. (We had been using a raw pointer to character string, which surely is NOT a valid Node.) This doesn't cause any backwards compatibility problems for stored rules, since raw unanalyzed parsetrees are never stored.
-
由 Tom Lane 提交于
*last*, after all updating of system catalogs. In old code, an error detected during TypeRename left the relation hosed. Also, add a call to flush the relation's relcache entry, rather than trusting to shared cache invalidation to flush it for us.
-
由 Tom Lane 提交于
relation being dropped.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
! * themselves, they'll need to check the connection status if we ! * return an error. Alfred Perlstein
-
由 Bruce Momjian 提交于
-