diff options
| author | Fujii Masao <fujii@postgresql.org> | 2025-03-21 12:56:39 +0900 |
|---|---|---|
| committer | Fujii Masao <fujii@postgresql.org> | 2025-03-21 13:00:04 +0900 |
| commit | 40c959271279abf362b57ffe613c7db80e11fc23 (patch) | |
| tree | 59742b63e2df855b6c3605e7eb42ad0a9f335782 /src/backend/executor/nodeModifyTable.c | |
| parent | 13dd6f77265b9738d29eb33f2dcd6d9361e92700 (diff) | |
doc: Remove incorrect description about dropping replication slots.
pg_drop_replication_slot() can drop replication slots created on
a different database than the one where it is executed. This behavior
has been in place since PostgreSQL 9.4, when pg_drop_replication_slot()
was introduced.
However, commit ff539d mistakenly added the following incorrect
description in the documentation:
For logical slots, this must be called when connected to
the same database the slot was created on.
This commit removes that incorrect statement. A similar mistake was
also present in the documentation for the DROP_REPLICATION_SLOT
command, which has now been corrected as well.
Back-patch to all supported versions.
Author: Hayato Kuroda <kuroda.hayato@fujitsu.com>
Reviewed-by: Fujii Masao <masao.fujii@gmail.com>
Discussion: https://postgr.es/m/OSCPR01MB14966C6BE304B5BB2E58D4009F5DE2@OSCPR01MB14966.jpnprd01.prod.outlook.com
Backpatch-through: 13
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions