- 05 5月, 2000 12 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Mount 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Thanks Andreas
-
由 Tom Lane 提交于
to need this updatepgproc.sql script after all...
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Rearrange handling of VACUUMs so that they are certain to be executed as superuser not some random user; also, do not forget to vacuum template1 itself.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
failure of rename() call.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
-
- 04 5月, 2000 1 次提交
-
-
由 Tom Lane 提交于
available C++ header files.
-
- 03 5月, 2000 8 次提交
-
-
由 Peter Mount 提交于
-
由 Hiroshi Inoue 提交于
postgres.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Thomas G. Lockhart 提交于
hub.org:/home/projects/pgsql/ftp/www/html/users-lounge/7.0/docs/
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
-
由 Bruce Momjian 提交于
-
- 02 5月, 2000 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tatsuo Ishii 提交于
pg_char_to_encoding() in multibyte disbaled case so that it does not throw an error, rather return HARD CODED default value (currently SQL_ASCII). This would solve the "non-mb backend vs. mb-enabled frontend" problem.
-
- 01 5月, 2000 2 次提交
-
-
由 Tom Lane 提交于
cleanup, ie, as soon as we have caught the longjmp. This ensures that current context will be a valid context throughout error cleanup. Before it was possible that current context was pointing at a context that would get deleted during cleanup, leaving any subsequent pallocs in deep trouble. I was able to provoke an Assert failure when compiled with asserts + -DCLOBBER_FREED_MEMORY, if I did something that would cause an error to be reported by the backend large-object code, because indeed that code operates in a context that gets deleted partway through xact abort --- and CurrentMemoryContext was still pointing at it! Boo hiss.
-
由 Tom Lane 提交于
loops, but just arbitrarily failing at 1000 locks.
-
- 29 4月, 2000 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 28 4月, 2000 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
because StatFp never got set in that case. Set it immediately before use to eliminate such problems.
-
由 Tom Lane 提交于
field value being displayed; produced coredump instead of the expected <NULL> display.
-
由 Tom Lane 提交于
thus causing failure if one sub-select had resjunk entries that the other did not (cf. bug report from Espinosa 4/27/00).
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
cases where joinclauses were present but some joins have to be made by cartesian-product join anyway. An example is SELECT * FROM a,b,c WHERE (a.f1 + b.f2 + c.f3) = 0; Even though all the rels have joinclauses, we must join two of them in cartesian style before we can use the join clause...
-
- 27 4月, 2000 1 次提交
-
-
由 Tom Lane 提交于
that might be hanging about. Now it does ... amazing nobody noticed this before ...
-