diff options
| author | Robert Haas <rhaas@postgresql.org> | 2017-09-26 08:58:06 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2017-09-26 09:01:43 -0400 |
| commit | 79a4a665c046af91d4216fe69b535c429039d0d0 (patch) | |
| tree | 1665da39235b60d397fd2787e3bbc85cafcad6e3 /src | |
| parent | 899bd785c0edf376077d3f5d65c316f92c1b64b5 (diff) | |
| download | postgresql-79a4a665c046af91d4216fe69b535c429039d0d0.tar.gz postgresql-79a4a665c046af91d4216fe69b535c429039d0d0.zip | |
Fix trivial mistake in README.
You might think I (Robert) could manage to count to five without
messing it up, but if you did, you would be wrong.
Amit Kapila
Discussion: http://postgr.es/m/CAA4eK1JxqqcuC5Un7YLQVhOYSZBS+t=3xqZuEkt5RyquyuxpwQ@mail.gmail.com
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/access/hash/README | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/hash/README b/src/backend/access/hash/README index 5827389a70a..bb90722778f 100644 --- a/src/backend/access/hash/README +++ b/src/backend/access/hash/README @@ -434,7 +434,7 @@ concurrent scan could start in that bucket before we've finished vacuuming it. If a scan gets ahead of cleanup, we could have the following problem: (1) the scan sees heap TIDs that are about to be removed before they are processed by VACUUM, (2) the scan decides that one or more of those TIDs are dead, (3) -VACUUM completes, (3) one or more of the TIDs the scan decided were dead are +VACUUM completes, (4) one or more of the TIDs the scan decided were dead are reused for an unrelated tuple, and finally (5) the scan wakes up and erroneously kills the new tuple. |