diff options
| author | Andres Freund <andres@anarazel.de> | 2019-01-21 17:03:15 -0800 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2019-01-21 17:07:10 -0800 |
| commit | c91560defc57f89f7e88632ea14ae77b5cec78ee (patch) | |
| tree | 250740f86c98f29eb20bdacf816ced13579c6a92 /src/backend/utils/cache | |
| parent | b7eda3e0e33402a7727253e6f307ca96b92eb23d (diff) | |
| download | postgresql-c91560defc57f89f7e88632ea14ae77b5cec78ee.tar.gz postgresql-c91560defc57f89f7e88632ea14ae77b5cec78ee.zip | |
Move remaining code from tqual.[ch] to heapam.h / heapam_visibility.c.
Given these routines are heap specific, and that there will be more
generic visibility support in via table AM, it makes sense to move the
prototypes to heapam.h (routines like HeapTupleSatisfiesVacuum will
not be exposed in a generic fashion, because they are too storage
specific).
Similarly, the code in tqual.c is specific to heap, so moving it into
access/heap/ makes sense.
Author: Andres Freund
Discussion: https://postgr.es/m/20180703070645.wchpu5muyto5n647@alap3.anarazel.de
Diffstat (limited to 'src/backend/utils/cache')
| -rw-r--r-- | src/backend/utils/cache/inval.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/utils/cache/inval.c b/src/backend/utils/cache/inval.c index b9f698ef2ce..16903c25f45 100644 --- a/src/backend/utils/cache/inval.c +++ b/src/backend/utils/cache/inval.c @@ -8,9 +8,9 @@ * When a tuple is updated or deleted, our standard time qualification rules * consider that it is *still valid* so long as we are in the same command, * ie, until the next CommandCounterIncrement() or transaction commit. - * (See utils/time/tqual.c, and note that system catalogs are generally - * scanned under the most current snapshot available, rather than the - * transaction snapshot.) At the command boundary, the old tuple stops + * (See acces/heap/heapam_visibility.c, and note that system catalogs are + * generally scanned under the most current snapshot available, rather than + * the transaction snapshot.) At the command boundary, the old tuple stops * being valid and the new version, if any, becomes valid. Therefore, * we cannot simply flush a tuple from the system caches during heap_update() * or heap_delete(). The tuple is still good at that point; what's more, |