rust/neon
1
0
Fork 0
mirror of https://github.com/neondatabase/neon.git synced 2025-12-22 21:59:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update links in synthetic-size.md (#8501)

Browse Source
This commit is contained in:
Mihai Bojin
2024-07-26 01:14:12 +01:00
committed by GitHub
parent 9bfa180f2e
commit 857a1823fe
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/synthetic-size.md
View File

@@ -21,9 +21,9 @@ implementation where we keep more data than we would need to, do not
change the synthetic size or incur any costs to the user. change the synthetic size or incur any costs to the user.
The synthetic size is calculated for the whole project. It is not The synthetic size is calculated for the whole project. It is not
straightforward to attribute size to individual branches. See "What is straightforward to attribute size to individual branches. See [What is
the size of an individual branch?" for discussion on those the size of an individual branch?](#what-is-the-size-of-an-individual-branch)
difficulties. for a discussion of those difficulties.
The synthetic size is designed to: The synthetic size is designed to:
@@ -40,8 +40,9 @@ The synthetic size is designed to:
- logical size is the size of a branch *at a given point in - logical size is the size of a branch *at a given point in
time*. It's the total size of all tables in all databases, as you time*. It's the total size of all tables in all databases, as you
see with "\l+" in psql for example, plus the Postgres SLRUs and some see with "\l+" in psql for example, plus the Postgres SLRUs and some
small amount of metadata. NOTE that currently, Neon does not include small amount of metadata. Note that currently, Neon does not include
the SLRUs and metadata in the logical size. See comment to `get_current_logical_size_non_incremental()`. the SLRUs and metadata in the logical size. Refer to the comment in
[`get_current_logical_size_non_incremental()`](/pageserver/src/pgdatadir_mapping.rs#L813-L814).
- a "point in time" is defined as an LSN value. You can convert a - a "point in time" is defined as an LSN value. You can convert a
timestamp to an LSN, but the storage internally works with LSNs. timestamp to an LSN, but the storage internally works with LSNs.