alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

[docs] Fix malformed link

Browse Source 
Removed duplicate colon that preceded link definition.
This commit is contained in:
roldanbob 2021-08-24 18:23:09 -04:00 committed by GitHub
parent af83218f47
commit 5db43c853e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/modules/ROOT/pages/connectors/postgresql.adoc
View File

@ -1703,7 +1703,7 @@ For format details, see http://www.opengeospatial.org/standards/sfa[Open Geospat
[id="postgresql-toasted-values"] [id="postgresql-toasted-values"]
=== Toasted values === Toasted values
PostgreSQL has a hard limit on the page size. PostgreSQL has a hard limit on the page size.
This means that values that are larger than around 8 KBs need to be stored by using link::https://www.postgresql.org/docs/current/storage-toast.html[TOAST storage]. This means that values that are larger than around 8 KBs need to be stored by using link:https://www.postgresql.org/docs/current/storage-toast.html[TOAST storage].
This impacts replication messages that are coming from the database. Values that were stored by using the TOAST mechanism and that have not been changed are not included in the message, unless they are part of the table's replica identity. This impacts replication messages that are coming from the database. Values that were stored by using the TOAST mechanism and that have not been changed are not included in the message, unless they are part of the table's replica identity.
There is no safe way for {prodname} to read the missing value out-of-bands directly from the database, as this would potentially lead to race conditions. Consequently, {prodname} follows these rules to handle toasted values: There is no safe way for {prodname} to read the missing value out-of-bands directly from the database, as this would potentially lead to race conditions. Consequently, {prodname} follows these rules to handle toasted values: