database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-26 12:21:12 +03:00
Code Activity

Fix handling of partitioned index in RelationGetNumberOfBlocksInFork()

Browse Source 
Since a partitioned index doesn't have storage, getting the number of
blocks from it will not give sensible results.  Existing callers
already check that they don't call it that way, so there doesn't
appear to be a live problem.  But for correctness, handle
RELKIND_PARTITIONED_INDEX together with the other non-storage
relkinds.

Reviewed-by: Michael Paquier <michael@paquier.xyz>
Reviewed-by: Alvaro Herrera <alvherre@alvh.no-ip.org>
Discussion: https://www.postgresql.org/message-id/1d3a5fbe-f48b-8bea-80da-9a5c4244aef9@enterprisedb.com
This commit is contained in:
Peter Eisentraut
2021-08-26 08:48:07 +02:00
parent 78ab944cd4
commit 0d906b2c0b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/backend/storage/buffer/bufmgr.c
View File

@ -2929,7 +2929,6 @@ RelationGetNumberOfBlocksInFork(Relation relation, ForkNumber forkNum)
{ {
case RELKIND_SEQUENCE: case RELKIND_SEQUENCE:
case RELKIND_INDEX: case RELKIND_INDEX:
case RELKIND_PARTITIONED_INDEX:
return smgrnblocks(RelationGetSmgr(relation), forkNum); return smgrnblocks(RelationGetSmgr(relation), forkNum);
case RELKIND_RELATION: case RELKIND_RELATION:
@ -2951,6 +2950,7 @@ RelationGetNumberOfBlocksInFork(Relation relation, ForkNumber forkNum)
case RELKIND_VIEW: case RELKIND_VIEW:
case RELKIND_COMPOSITE_TYPE: case RELKIND_COMPOSITE_TYPE:
case RELKIND_FOREIGN_TABLE: case RELKIND_FOREIGN_TABLE:
case RELKIND_PARTITIONED_INDEX:
case RELKIND_PARTITIONED_TABLE: case RELKIND_PARTITIONED_TABLE:
default: default:
Assert(false); Assert(false);