aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2020-07-03 12:08:35 +0900
committerFujii Masao <fujii@postgresql.org>2020-07-03 12:09:07 +0900
commit95a604eaebd145729d9f8c936b37703a212f27fd (patch)
tree9707d7a3db743790c7ee8e16d69a4a57dc35369e /src/backend/executor/nodeModifyTable.c
parent8d459762b10372e48845a49b305f4e1e165fe173 (diff)
downloadpostgresql-95a604eaebd145729d9f8c936b37703a212f27fd.tar.gz
postgresql-95a604eaebd145729d9f8c936b37703a212f27fd.zip
doc: Correct description of restart_lsn in pg_replication_slots
Previously the document explained that restart_lsn indicates the LSN of oldest WAL won't be automatically removed during checkpoints. But since v13 this was no longer true thanks to max_slot_wal_keep_size. Back-patch to v13 where max_slot_wal_keep_size was added. Author: Fujii Masao Discussion: https://postgr.es/m/6497f1e9-3148-c5da-7e49-b2fddad9a42f@oss.nttdata.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions