diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2024-03-03 19:38:22 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2024-03-03 19:38:22 +0200 |
| commit | 024c521117579a6d356050ad3d78fdc95e44eefa (patch) | |
| tree | 27a2d9588eefc43c4bc3ac7b31f8a6740a2de34b /src/backend/commands/sequence.c | |
| parent | ab355e3a88de745607f6dd4c21f0119b5c68f2ad (diff) | |
| download | postgresql-024c521117579a6d356050ad3d78fdc95e44eefa.tar.gz postgresql-024c521117579a6d356050ad3d78fdc95e44eefa.zip | |
Replace BackendIds with 0-based ProcNumbers
Now that BackendId was just another index into the proc array, it was
redundant with the 0-based proc numbers used in other places. Replace
all usage of backend IDs with proc numbers.
The only place where the term "backend id" remains is in a few pgstat
functions that expose backend IDs at the SQL level. Those IDs are now
in fact 0-based ProcNumbers too, but the documentation still calls
them "backend ids". That term still seems appropriate to describe what
the numbers are, so I let it be.
One user-visible effect is that pg_temp_0 is now a valid temp schema
name, for backend with ProcNumber 0.
Reviewed-by: Andres Freund
Discussion: https://www.postgresql.org/message-id/8171f1aa-496f-46a6-afc3-c46fe7a9b407@iki.fi
Diffstat (limited to 'src/backend/commands/sequence.c')
| -rw-r--r-- | src/backend/commands/sequence.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/commands/sequence.c b/src/backend/commands/sequence.c index 24b9ee42c2a..46103561c31 100644 --- a/src/backend/commands/sequence.c +++ b/src/backend/commands/sequence.c @@ -343,7 +343,7 @@ fill_seq_with_data(Relation rel, HeapTuple tuple) { SMgrRelation srel; - srel = smgropen(rel->rd_locator, InvalidBackendId); + srel = smgropen(rel->rd_locator, INVALID_PROC_NUMBER); smgrcreate(srel, INIT_FORKNUM, false); log_smgrcreate(&rel->rd_locator, INIT_FORKNUM); fill_seq_fork_with_data(rel, tuple, INIT_FORKNUM); |