- 23 11月, 1999 7 次提交
-
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
see that this should be a worse way to fail to open a file than any other.
-
由 Tom Lane 提交于
userid in the flat password file. Do it enough times and the postmaster panicked :-(
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Make all system indexes unique. Make all cache loads use system indexes. Rename *rel to *relid in inheritance tables. Rename cache names to be clearer.
-
- 22 11月, 1999 7 次提交
-
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
for the case of errors in backend startup, and proc_exit's method for coping with errors during proc_exit was *completely* busted. Fixed per discussions on pghackers around 11/6/99.
-
由 Tom Lane 提交于
ReleaseRelationBuffers --- need to wait if anyone is trying to flush out that buffer.
-
由 Tom Lane 提交于
it wants to release. This leads to a race condition: does the backend that's trying to flush the buffer do so before the one that's deleting the relation does so? Usually no problem, I expect, but on occasion this could lead to hard-to-reproduce complaints from md.c, especially mdblindwrt.
-
由 Tom Lane 提交于
returns a list of RelOptInfos, eliminating the need for static state in index_info. That static state was a direct cause of coredumps; if anything decided to elog(ERROR) partway through an index_info search of pg_index, the next query would try to close a scan pointer that was pointing at no-longer-valid memory. Another example of the reasons to avoid static state variables...
-
由 Tom Lane 提交于
of the index it wants to destroy. This ensures that no other backend is actively scanning or updating that index. Getting exclusive access on the index alone is NOT sufficient, because the executor is rather cavalier about getting locks on indexes --- see ExecOpenIndices(). It might be better to grab index locks in the executor, but I'm not sure the extra lockmanager traffic is really worth it just to make index_destroy cleaner.
-
由 Tom Lane 提交于
-
- 21 11月, 1999 6 次提交
-
-
由 Tom Lane 提交于
(whoever thought world-writable files were a good default????). Modify the pg_pwd code so that pg_pwd is created with 600 permissions. Modify initdb so that permissions on a pre-existing PGDATA directory are not blindly accepted: if the dir is already there, it does chmod go-rwx to be sure that the permissions are OK and the dir actually is owned by postgres.
-
由 Tom Lane 提交于
inval.c thought it could safely use the catcache to look up the OIDs of system relations. Not good, considering that inval.c could be called during catcache loading, if a shared-inval message arrives. Rip out the lookup logic and instead use the known OIDs from pg_class.h.
-
由 Tom Lane 提交于
as that test finishes --- helps to give the impression that something is happening...
-
由 Tom Lane 提交于
to be accepted, but constraints regress test was expecting it to fail.
-
由 Tom Lane 提交于
table defaults or rules: translate them to a function call so that parse_coerce doesn't reduce them to a date or time constant immediately. Also, eliminate a lot of redundancy in the expression grammar by defining a new nonterminal com_expr, which contains all the productions that can be shared by a_expr and b_expr.
-
由 Tom Lane 提交于
script. This is way cool...
-
- 20 11月, 1999 1 次提交
-
-
由 Jan Wieck 提交于
Jan
-
- 19 11月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 18 11月, 1999 4 次提交
-
-
由 Jan Wieck 提交于
compressed lztext data type. Jan
-
由 Bruce Momjian 提交于
-
由 Jan Wieck 提交于
HAVE the required OID's first. Jan
-
由 Jan Wieck 提交于
Jan
-
- 17 11月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 16 11月, 1999 2 次提交
-
-
由 Tom Lane 提交于
Warn_restart has been set by the backend main loop. This means that elog(ERROR) or elog(FATAL) in the postmaster or during backend startup now have well-defined behavior: proc_exit() rather than coredump. In the case of elog() inside the postmaster, I think that proc_exit() is probably not enough --- don't we want our child backends to be forced to quit too? But I don't understand Vadim's recent changes in this area, so I'll leave it to him to look over and tweak if needed.
-
由 Bruce Momjian 提交于
Thanks to Tom Lane for ideas.
-
- 15 11月, 1999 8 次提交
-
-
由 Tatsuo Ishii 提交于
This fix is reported by Hiroki Kataoka (kataoka@interwiz.koganei.tokyo.jp).
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
subselects can only appear on the righthand side of a binary operator. That's still true for quantified predicates like x = ANY (SELECT ...), but a subselect that delivers a single result can now appear anywhere in an expression. This is implemented by changing EXPR_SUBLINK sublinks to represent just the (SELECT ...) expression, without any 'left hand side' or combining operator --- so they're now more like EXISTS_SUBLINK. To handle the case of '(x, y, z) = (SELECT ...)', I added a new sublink type MULTIEXPR_SUBLINK, which acts just like EXPR_SUBLINK used to. But the grammar will only generate one for a multiple-left-hand-side row expression.
-
由 Tom Lane 提交于
and pg_amop have indexes.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
versions of gmake.
-
由 Bruce Momjian 提交于
-
- 14 11月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
descriptions enabled.
-
- 13 11月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
circumstances: => select * from foo\x\t\pset border 0 \p\g\\select * from bar; Also the release prep update so the sql_help.h is generated before packaging. Peter.
-