- 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 提交于
-
- 25 5月, 2000 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tatsuo Ishii 提交于
(it returns error with errno ECHILD upon successful completion of commands). This fix ignores an error from system() if errno == ECHILD.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
- 24 5月, 2000 7 次提交
-
-
由 Marc G. Fournier 提交于
add a --with-setproctitle switch to configure that leaves the use of setproctitle() disabled by default ...
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
what to do.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
think that both sides of indexqual look like index keys. An example is create table inside (f1 float8 primary key); create table outside (g1 float8, g2 float8); select * from inside,outside where f1 = atan2(g1+1, g2); ERROR: ExecInitIndexScan: both left and right ops are rel-vars (note that failure is potentially platform-dependent). Solution is a cleanup I had had in mind to make anyway: functional index keys should be represented as Var nodes in the fixed indexqual, just like regular index keys.
-
- 23 5月, 2000 3 次提交
-
-
由 Tom Lane 提交于
it exists) before testing 'using namespace std'. This is necessary on some C++ setups where the compiler won't take a 'using' until you've included a header that mentions namespace std. (Pretty braindead if you ask me, but...)
-
由 Tom Lane 提交于
--with-includes) to makefiles for pltcl and plperl, so that these switches will be used even though we do not want other top-level CFLAGS. Ain't it fun trying to support multiple-compiler platforms?
-
由 Tom Lane 提交于
-