diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2024-10-31 10:09:40 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2024-10-31 10:09:40 +0200 |
| commit | 2b9b8ebbf8a2f621d1cecc4db759700f9ce6ce66 (patch) | |
| tree | 12a4c26e04fafc85ef9ca973767d3675c8b5ab8a /src/backend/executor/nodeBitmapHeapscan.c | |
| parent | 8e2e2662214a0a6d0fb23a070ea78d691d8ced43 (diff) | |
| download | postgresql-2b9b8ebbf8a2f621d1cecc4db759700f9ce6ce66.tar.gz postgresql-2b9b8ebbf8a2f621d1cecc4db759700f9ce6ce66.zip | |
Split RelationClearRelation into three different functions
The old RelationClearRelation function did different things depending
on the arguments and circumstances. It could:
a) remove the relation completely from relcache (rebuild == false),
b) mark the entry as invalid (rebuild == true, but not in xact), or
c) rebuild the entry (rebuild == true).
Different callers used it for different purposes, and often assumed a
particular behavior, which was confusing. Split it into three
different functions, one for each of the above actions (one of them,
RelationInvalidateRelation, was already added in commit e6cd857726).
Move the responsibility of choosing the action and calling the right
function to the callers.
Reviewed-by: jian he <jian.universality@gmail.com>
Discussion: https://www.postgresql.org/message-id/9c9e8908-7b3e-4ce7-85a8-00c0e165a3d6%40iki.fi
Diffstat (limited to 'src/backend/executor/nodeBitmapHeapscan.c')
0 files changed, 0 insertions, 0 deletions