diff options
| author | Amit Kapila <akapila@postgresql.org> | 2022-02-14 08:24:44 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2022-02-14 08:24:44 +0530 |
| commit | caa231be97df3e4cb2667ea355562d5a5faa60c9 (patch) | |
| tree | ffdc418aabb12f2580b2e8f58c86de24d86f0693 /doc | |
| parent | ac2303aa0386d2fa26cc3e237076b49827b39d6a (diff) | |
| download | postgresql-caa231be97df3e4cb2667ea355562d5a5faa60c9.tar.gz | |
WAL log unchanged toasted replica identity key attributes.
Currently, during UPDATE, the unchanged replica identity key attributes
are not logged separately because they are getting logged as part of the
new tuple. But if they are stored externally then the untoasted values are
not getting logged as part of the new tuple and logical replication won't
be able to replicate such UPDATEs. So we need to log such attributes as
part of the old_key_tuple during UPDATE.
Reported-by: Haiying Tang
Author: Dilip Kumar and Amit Kapila
Reviewed-by: Alvaro Herrera, Haiying Tang, Andres Freund
Backpatch-through: 10
Discussion: https://postgr.es/m/OS0PR01MB611342D0A92D4F4BF26C0F47FB229@OS0PR01MB6113.jpnprd01.prod.outlook.com
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/src/sgml/ref/alter_table.sgml | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index ca959391ef..2eced5d65b 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -819,10 +819,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <listitem> <para> This form changes the information which is written to the write-ahead log - to identify rows which are updated or deleted. This option has no effect - except when logical replication is in use. - In all cases, no old values are logged unless at least one of the columns - that would be logged differs between the old and new versions of the row. + to identify rows which are updated or deleted. + In most cases, the old value of each column is only logged if it differs + from the new value; however, if the old value is stored externally, it is + always logged regardless of whether it changed. + This option has no effect except when logical replication is in use. <variablelist> <varlistentry> <term><literal>DEFAULT</literal></term> |