public inbox for [email protected]
help / color / mirror / Atom feedpgsql: doc: Remove incorrect description about dropping replication slo
6+ messages / 1 participants
[nested] [flat]
* pgsql: doc: Remove incorrect description about dropping replication slo
@ 2025-03-21 04:04 Fujii Masao <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Fujii Masao @ 2025-03-21 04:04 UTC (permalink / raw)
To: [email protected]
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 <[email protected]>
Reviewed-by: Fujii Masao <[email protected]>
Discussion: https://postgr.es/m/OSCPR01MB14966C6BE304B5BB2E58D4009F5DE2@OSCPR01MB14966.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/14413d0ef5df4df4cad36cfe657e3f9d1f94bc2f
Modified Files
--------------
doc/src/sgml/func.sgml | 3 +--
doc/src/sgml/protocol.sgml | 2 --
2 files changed, 1 insertion(+), 4 deletions(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: doc: Remove incorrect description about dropping replication slo
@ 2025-03-21 04:05 Fujii Masao <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Fujii Masao @ 2025-03-21 04:05 UTC (permalink / raw)
To: [email protected]
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 <[email protected]>
Reviewed-by: Fujii Masao <[email protected]>
Discussion: https://postgr.es/m/OSCPR01MB14966C6BE304B5BB2E58D4009F5DE2@OSCPR01MB14966.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/97ce4d375a0ada1c1dd2f23552b40eadf5ecf14e
Modified Files
--------------
doc/src/sgml/func.sgml | 3 +--
doc/src/sgml/protocol.sgml | 2 --
2 files changed, 1 insertion(+), 4 deletions(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: doc: Remove incorrect description about dropping replication slo
@ 2025-03-21 04:05 Fujii Masao <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Fujii Masao @ 2025-03-21 04:05 UTC (permalink / raw)
To: [email protected]
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 <[email protected]>
Reviewed-by: Fujii Masao <[email protected]>
Discussion: https://postgr.es/m/OSCPR01MB14966C6BE304B5BB2E58D4009F5DE2@OSCPR01MB14966.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/9070e5840aa30c51c0e4040d9e4a9ba1964aee07
Modified Files
--------------
doc/src/sgml/func.sgml | 3 +--
doc/src/sgml/protocol.sgml | 2 --
2 files changed, 1 insertion(+), 4 deletions(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: doc: Remove incorrect description about dropping replication slo
@ 2025-03-21 04:05 Fujii Masao <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Fujii Masao @ 2025-03-21 04:05 UTC (permalink / raw)
To: [email protected]
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 <[email protected]>
Reviewed-by: Fujii Masao <[email protected]>
Discussion: https://postgr.es/m/OSCPR01MB14966C6BE304B5BB2E58D4009F5DE2@OSCPR01MB14966.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/40c959271279abf362b57ffe613c7db80e11fc23
Modified Files
--------------
doc/src/sgml/func.sgml | 3 +--
doc/src/sgml/protocol.sgml | 2 --
2 files changed, 1 insertion(+), 4 deletions(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: doc: Remove incorrect description about dropping replication slo
@ 2025-03-21 04:05 Fujii Masao <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Fujii Masao @ 2025-03-21 04:05 UTC (permalink / raw)
To: [email protected]
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 <[email protected]>
Reviewed-by: Fujii Masao <[email protected]>
Discussion: https://postgr.es/m/OSCPR01MB14966C6BE304B5BB2E58D4009F5DE2@OSCPR01MB14966.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/ae0696ed32316d0c0a82d55fd54a21c9947bb181
Modified Files
--------------
doc/src/sgml/func.sgml | 3 +--
doc/src/sgml/protocol.sgml | 2 --
2 files changed, 1 insertion(+), 4 deletions(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: doc: Remove incorrect description about dropping replication slo
@ 2025-03-21 04:06 Fujii Masao <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Fujii Masao @ 2025-03-21 04:06 UTC (permalink / raw)
To: [email protected]
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 <[email protected]>
Reviewed-by: Fujii Masao <[email protected]>
Discussion: https://postgr.es/m/OSCPR01MB14966C6BE304B5BB2E58D4009F5DE2@OSCPR01MB14966.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
------
REL_13_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/c6002659fbd7757864da4d4f53a3261ff0103bc6
Modified Files
--------------
doc/src/sgml/func.sgml | 3 +--
doc/src/sgml/protocol.sgml | 2 --
2 files changed, 1 insertion(+), 4 deletions(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-03-21 04:06 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-03-21 04:04 pgsql: doc: Remove incorrect description about dropping replication slo Fujii Masao <[email protected]>
2025-03-21 04:05 pgsql: doc: Remove incorrect description about dropping replication slo Fujii Masao <[email protected]>
2025-03-21 04:05 pgsql: doc: Remove incorrect description about dropping replication slo Fujii Masao <[email protected]>
2025-03-21 04:05 pgsql: doc: Remove incorrect description about dropping replication slo Fujii Masao <[email protected]>
2025-03-21 04:05 pgsql: doc: Remove incorrect description about dropping replication slo Fujii Masao <[email protected]>
2025-03-21 04:06 pgsql: doc: Remove incorrect description about dropping replication slo Fujii Masao <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox