- 03 6月, 1999 7 次提交
-
-
由 Vadim B. Mikheev 提交于
transactions will not assume that MyProc transaction was committed before snapshot calculations. With old MyProc->xid assignment (in xact.c:StartTransaction()) there was ability to see the same row twice (I used gdb for this)!... 2. Assignments of InvalidTransactionId to MyProc->xid and MyProc->xmin are moved from xact.c:CommitTransaction() to xact.c:RecordTransactionCommit() - this invalidation must be done before releasing transaction locks or bad (too high) XmaxRecent value might be used by vacuum ("ERROR: Child itemid marked as unused" reported by "Hiroshi Inoue" <Inoue@tpf.co.jp>; once again, gdb allowed me reproduce this error).
-
由 Thomas G. Lockhart 提交于
Clean out duplicate stuff in odbc.sgml resulting from a faulty patch.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
-
由 Tom Lane 提交于
because it ignored the LOs themselves but failed to ignore the indexes on the LOs. How long has this been broken??
-
由 Tom Lane 提交于
all the expected keys (it was returning uninitialized memory).
-
由 Tom Lane 提交于
libpq ...
-
- 02 6月, 1999 3 次提交
-
-
由 Jan Wieck 提交于
Jan
-
由 Bruce Momjian 提交于
198.68.123.0/27 the same when indexing them. D'Arcy
-
由 Thomas G. Lockhart 提交于
Multiple intros cause trouble since they have some section elements (e.g. "y2k.sgml") in common leading to duplicate labels. Include emacs formatting hints in the intro*.sgml sources.
-
- 01 6月, 1999 9 次提交
-
-
由 Vadim B. Mikheev 提交于
{ Oid relId; Oid dbId; union { BlockNumber blkno; TransactionId xid; } objId; > > Added: > /* > * offnum should be part of objId.tupleId above, but would increase > * sizeof(LOCKTAG) and so moved here; currently used by userlocks only. > */ > OffsetNumber offnum; uint16 lockmethod; /* needed by userlocks */ } LOCKTAG; gmake clean required... User locks are ready for 6.5 release...
-
由 Bruce Momjian 提交于
Vince.
-
由 Bruce Momjian 提交于
later. Vince.
-
由 Tom Lane 提交于
all fields that should be set). Add a MoveToFront primitive to speed up one of the hotspots in SearchSysCache.
-
由 Tom Lane 提交于
memory context at transaction commit or abort.
-
由 Tom Lane 提交于
in an index doesn't have a restriction selectivity estimator.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
right circumstances it would leave old and new bucket headers pointing to the same list of records.
-
由 Bruce Momjian 提交于
-
- 31 5月, 1999 1 次提交
-
-
由 Vadim B. Mikheev 提交于
(no sense to hold it) or we'll be out of lock entries. Great thanks to Hiroshi Inoue.
-
- 30 5月, 1999 5 次提交
-
-
由 Tom Lane 提交于
(Curious that gcc doesn't complain about this code...).
-
由 Tom Lane 提交于
is poor coding style. I agree.
-
由 Tom Lane 提交于
file headers, to conform to established Postgres coding style and avoid warnings from gcc.
-
由 Tom Lane 提交于
after checking for presence of C++ compiler. Odd we hadn't seen any reports of problems before...
-
由 Tom Lane 提交于
when used with egcs --- now it does.
-
- 29 5月, 1999 7 次提交
-
-
由 Vadim B. Mikheev 提交于
2. Get rid of locking when updating statistics in vacuum. 3. Use QuerySnapshot in COPY TO and call SetQuerySnashot in main tcop loop before FETCH and COPY TO.
-
由 Vadim B. Mikheev 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
few percent speedup in INSERT...
-
由 Tom Lane 提交于
redundant) SearchSysCache searches per table column in an INSERT, which accounted for a good percentage of the CPU time for INSERT ... VALUES(). Now it only does two searches in the typical case.
-
由 Tom Lane 提交于
cache access routines.
-
由 Tom Lane 提交于
through MAXBACKENDS array entries used to be fine when MAXBACKENDS = 64. It's not so cool with MAXBACKENDS = 1024 (or more!), especially not in a frequently-used routine like SIDelExpiredDataEntries. Repair by making procState array size be the soft MaxBackends limit rather than the hard limit, and by converting SIGetProcStateLimit() to a macro.
-
- 28 5月, 1999 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
do the right thing: look for a NOTICE message from the backend before we close our side of the socket. 6.4 libpq did not reliably print the backend's hara-kiri message, 'The Postmaster has informed me ...', because it only did the right thing if connection closure was detected during a read attempt instead of a write attempt.
-
由 Bruce Momjian 提交于
new -x option to skip acl dump.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
-
- 27 5月, 1999 2 次提交
-
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
Update for v6.5 release.
-