Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
87f830e0
Commit
87f830e0
authored
10 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Adjust cutoff points in newly-added sanity tests.
Per recommendation from Andres.
parent
78db307b
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/backend/commands/vacuum.c
+15
-7
15 additions, 7 deletions
src/backend/commands/vacuum.c
with
15 additions
and
7 deletions
src/backend/commands/vacuum.c
+
15
−
7
View file @
87f830e0
...
...
@@ -745,13 +745,13 @@ vac_update_relstats(Relation relation,
* which case we don't want to forget the work it already did. However,
* if the stored relfrozenxid is "in the future", then it must be corrupt
* and it seems best to overwrite it with the cutoff we used this time.
*
See
vac_update_datfrozenxid() concerning what we consider
to be "in the
* future".
*
This should match
vac_update_datfrozenxid() concerning what we consider
*
to be "in the
future".
*/
if
(
TransactionIdIsNormal
(
frozenxid
)
&&
pgcform
->
relfrozenxid
!=
frozenxid
&&
(
TransactionIdPrecedes
(
pgcform
->
relfrozenxid
,
frozenxid
)
||
TransactionIdPrecedes
(
GetOldestXmin
(
NULL
,
true
),
TransactionIdPrecedes
(
ReadNewTransactionId
(
),
pgcform
->
relfrozenxid
)))
{
pgcform
->
relfrozenxid
=
frozenxid
;
...
...
@@ -762,7 +762,7 @@ vac_update_relstats(Relation relation,
if
(
MultiXactIdIsValid
(
minmulti
)
&&
pgcform
->
relminmxid
!=
minmulti
&&
(
MultiXactIdPrecedes
(
pgcform
->
relminmxid
,
minmulti
)
||
MultiXactIdPrecedes
(
GetOldes
tMultiXactId
(),
pgcform
->
relminmxid
)))
MultiXactIdPrecedes
(
ReadNex
tMultiXactId
(),
pgcform
->
relminmxid
)))
{
pgcform
->
relminmxid
=
minmulti
;
dirty
=
true
;
...
...
@@ -803,8 +803,8 @@ vac_update_datfrozenxid(void)
SysScanDesc
scan
;
HeapTuple
classTup
;
TransactionId
newFrozenXid
;
TransactionId
lastSaneFrozenXid
;
MultiXactId
newMinMulti
;
TransactionId
lastSaneFrozenXid
;
MultiXactId
lastSaneMinMulti
;
bool
bogus
=
false
;
bool
dirty
=
false
;
...
...
@@ -815,13 +815,21 @@ vac_update_datfrozenxid(void)
* committed pg_class entries for new tables; see AddNewRelationTuple().
* So we cannot produce a wrong minimum by starting with this.
*/
newFrozenXid
=
lastSaneFrozenXid
=
GetOldestXmin
(
NULL
,
true
);
newFrozenXid
=
GetOldestXmin
(
NULL
,
true
);
/*
* Similarly, initialize the MultiXact "min" with the value that would be
* used on pg_class for new tables. See AddNewRelationTuple().
*/
newMinMulti
=
lastSaneMinMulti
=
GetOldestMultiXactId
();
newMinMulti
=
GetOldestMultiXactId
();
/*
* Identify the latest relfrozenxid and relminmxid values that we could
* validly see during the scan. These are conservative values, but it's
* not really worth trying to be more exact.
*/
lastSaneFrozenXid
=
ReadNewTransactionId
();
lastSaneMinMulti
=
ReadNextMultiXactId
();
/*
* We must seqscan pg_class to find the minimum Xid, because there is no
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment