public inbox for [email protected]
help / color / mirror / Atom feed[PATCH v20 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
20+ messages / 5 participants
[nested] [flat]
* [PATCH v19 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index e0dca81cb2..31a57943f7 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -101,7 +101,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2c107199d3..23522ccaf3 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -228,7 +228,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--oyUTqETQ0mS9luUI
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v19-0004-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v20 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index e0dca81cb2..31a57943f7 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -101,7 +101,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2c107199d3..23522ccaf3 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -228,7 +228,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--3V7upXqbjpZ4EhLz
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v20-0004-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v18 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index e0dca81cb2..31a57943f7 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -101,7 +101,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2c107199d3..23522ccaf3 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -228,7 +228,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--IJpNTDwzlM2Ie8A6
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v18-0004-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v13 5/7] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index 0d6be9a2fa..66a4de4762 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -100,7 +100,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2e271862fc..f1ff6bb451 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -233,7 +233,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--5vNYLRcllDrimb99
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v13-0006-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v18 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index e0dca81cb2..31a57943f7 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -101,7 +101,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2c107199d3..23522ccaf3 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -228,7 +228,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--IJpNTDwzlM2Ie8A6
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v18-0004-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v19 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index e0dca81cb2..31a57943f7 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -101,7 +101,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2c107199d3..23522ccaf3 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -228,7 +228,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--oyUTqETQ0mS9luUI
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v19-0004-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v20 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index e0dca81cb2..31a57943f7 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -101,7 +101,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2c107199d3..23522ccaf3 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -228,7 +228,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--3V7upXqbjpZ4EhLz
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v20-0004-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v14 5/7] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index 0d6be9a2fa..66a4de4762 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -100,7 +100,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2e271862fc..f1ff6bb451 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -233,7 +233,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--IS0zKkzwUGydFO0o
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v14-0006-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v15 5/7] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index 0d6be9a2fa..66a4de4762 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -100,7 +100,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2e271862fc..f1ff6bb451 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -233,7 +233,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--k+w/mQv8wyuph6w0
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v15-0006-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v12 4/6] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index 0d6be9a2fa..66a4de4762 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -100,7 +100,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2e271862fc..f1ff6bb451 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -233,7 +233,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--YiEDa0DAkWCtVeE4
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v12-0005-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v16 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index 4c63a7e768..b175152e6b 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -101,7 +101,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index f629524be0..b12a9f8dd5 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -233,7 +233,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--SLDf9lqlvOQaIe6s
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v16-0004-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v19 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index e0dca81cb2..31a57943f7 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -101,7 +101,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2c107199d3..23522ccaf3 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -228,7 +228,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--oyUTqETQ0mS9luUI
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v19-0004-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* [PATCH v18 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml
@ 2023-02-15 22:45 Nathan Bossart <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Nathan Bossart @ 2023-02-15 22:45 UTC (permalink / raw)
---
.../{archive-modules.sgml => archive-and-restore-modules.sgml} | 0
doc/src/sgml/filelist.sgml | 2 +-
doc/src/sgml/postgres.sgml | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
rename doc/src/sgml/{archive-modules.sgml => archive-and-restore-modules.sgml} (100%)
diff --git a/doc/src/sgml/archive-modules.sgml b/doc/src/sgml/archive-and-restore-modules.sgml
similarity index 100%
rename from doc/src/sgml/archive-modules.sgml
rename to doc/src/sgml/archive-and-restore-modules.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index e0dca81cb2..31a57943f7 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -101,7 +101,7 @@
<!ENTITY custom-scan SYSTEM "custom-scan.sgml">
<!ENTITY logicaldecoding SYSTEM "logicaldecoding.sgml">
<!ENTITY replication-origins SYSTEM "replication-origins.sgml">
-<!ENTITY archive-modules SYSTEM "archive-modules.sgml">
+<!ENTITY archive-and-restore-modules SYSTEM "archive-and-restore-modules.sgml">
<!ENTITY protocol SYSTEM "protocol.sgml">
<!ENTITY sources SYSTEM "sources.sgml">
<!ENTITY storage SYSTEM "storage.sgml">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 2c107199d3..23522ccaf3 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -228,7 +228,7 @@ break is not needed in a wider output rendering.
&bgworker;
&logicaldecoding;
&replication-origins;
- &archive-modules;
+ &archive-and-restore-modules;
</part>
--
2.25.1
--IJpNTDwzlM2Ie8A6
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="v18-0004-restructure-archive-modules-docs-in-preparation-.patch"
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: Align memory context level numbering in pg_log_backend_memory_contexts()
@ 2025-04-17 12:25 Rahila Syed <[email protected]>
2025-04-17 14:27 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() torikoshia <[email protected]>
2025-04-17 21:11 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
0 siblings, 2 replies; 20+ messages in thread
From: Rahila Syed @ 2025-04-17 12:25 UTC (permalink / raw)
To: pgsql-hackers
Hi,
> The attached patch is how I think we should do it.
>
Thank you for the patch.
I tested this patch and it works fine. I agree with the changes made in it.
Regarding v2 patch,
- int level = 0;
Retaining the level variable will enhance the code readability, IMO.
Thank you,
Rahila Syed
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: Align memory context level numbering in pg_log_backend_memory_contexts()
2025-04-17 12:25 Re: Align memory context level numbering in pg_log_backend_memory_contexts() Rahila Syed <[email protected]>
@ 2025-04-17 14:27 ` torikoshia <[email protected]>
1 sibling, 0 replies; 20+ messages in thread
From: torikoshia @ 2025-04-17 14:27 UTC (permalink / raw)
To: Rahila Syed <[email protected]>; [email protected]; +Cc: pgsql-hackers
Thanks for your review, Melih and Rahila.
On 2025-04-17 21:25, Rahila Syed wrote:
> Hi,
>
>> The attached patch is how I think we should do it.
>
> Thank you for the patch.
> I tested this patch and it works fine. I agree with the changes made
> in it.
>
> Regarding v2 patch,
> - int level = 0;
>
> Retaining the level variable will enhance the code readability, IMO.
As for the level variable, this change comes from the v1 patch, and I
don't have a strong opinion about it.
However, if we decide to keep the level variable here, it might be more
consistent to also define it in MemoryContextStatsDetail().
--
Regards,
--
Atsushi Torikoshi
Seconded from NTT DATA GROUP CORPORATION to SRA OSS K.K.
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: Align memory context level numbering in pg_log_backend_memory_contexts()
2025-04-17 12:25 Re: Align memory context level numbering in pg_log_backend_memory_contexts() Rahila Syed <[email protected]>
@ 2025-04-17 21:11 ` David Rowley <[email protected]>
2025-04-18 08:54 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() Fujii Masao <[email protected]>
1 sibling, 1 reply; 20+ messages in thread
From: David Rowley @ 2025-04-17 21:11 UTC (permalink / raw)
To: Rahila Syed <[email protected]>; +Cc: pgsql-hackers
On Fri, 18 Apr 2025 at 00:25, Rahila Syed <[email protected]> wrote:
> Regarding v2 patch,
> - int level = 0;
>
> Retaining the level variable will enhance the code readability, IMO.
When I read that, I suspected it might have been leftover from a
refactor during the development that was forgotten about. There'd be
thousands of places in our code base that you could make the
readability argument for, including the max_level and max_children
parameters at the same call-site. But those didn't get the same
treatment.
I've now pushed the latest patch. Thanks for the reviews.
David
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: Align memory context level numbering in pg_log_backend_memory_contexts()
2025-04-17 12:25 Re: Align memory context level numbering in pg_log_backend_memory_contexts() Rahila Syed <[email protected]>
2025-04-17 21:11 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
@ 2025-04-18 08:54 ` Fujii Masao <[email protected]>
2025-04-18 09:23 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
0 siblings, 1 reply; 20+ messages in thread
From: Fujii Masao @ 2025-04-18 08:54 UTC (permalink / raw)
To: David Rowley <[email protected]>; Rahila Syed <[email protected]>; +Cc: pgsql-hackers
On 2025/04/18 6:11, David Rowley wrote:
> On Fri, 18 Apr 2025 at 00:25, Rahila Syed <[email protected]> wrote:
>> Regarding v2 patch,
>> - int level = 0;
>>
>> Retaining the level variable will enhance the code readability, IMO.
>
> When I read that, I suspected it might have been leftover from a
> refactor during the development that was forgotten about. There'd be
> thousands of places in our code base that you could make the
> readability argument for, including the max_level and max_children
> parameters at the same call-site. But those didn't get the same
> treatment.
>
> I've now pushed the latest patch. Thanks for the reviews.
Shouldn't the example output of pg_log_backend_memory_contexts() in
the documentation also be updated to use 1-based numbering for consistency?
Patch attached.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From 7b3aa9de467005e540b2246ed89c9e43fe08f6bd Mon Sep 17 00:00:00 2001
From: Fujii Masao <[email protected]>
Date: Fri, 18 Apr 2025 17:45:29 +0900
Subject: [PATCH v1] doc: Fix memory context level in
pg_log_backend_memory_contexts() example.
Commit d9e03864b6b changed the memory context level numbers shown by
pg_log_backend_memory_contexts() to be 1-based. However, the example in
the documentation was not updated and still used 0-based numbering.
This commit updates the example to match the current 1-based output.
---
doc/src/sgml/func.sgml | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 1c5cfee25d1..574a544d9fa 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -28922,16 +28922,16 @@ One message for each memory context will be logged. For example:
<screen>
LOG: logging memory contexts of PID 10377
STATEMENT: SELECT pg_log_backend_memory_contexts(pg_backend_pid());
-LOG: level: 0; TopMemoryContext: 80800 total in 6 blocks; 14432 free (5 chunks); 66368 used
-LOG: level: 1; pgstat TabStatusArray lookup hash table: 8192 total in 1 blocks; 1408 free (0 chunks); 6784 used
-LOG: level: 1; TopTransactionContext: 8192 total in 1 blocks; 7720 free (1 chunks); 472 used
-LOG: level: 1; RowDescriptionContext: 8192 total in 1 blocks; 6880 free (0 chunks); 1312 used
-LOG: level: 1; MessageContext: 16384 total in 2 blocks; 5152 free (0 chunks); 11232 used
-LOG: level: 1; Operator class cache: 8192 total in 1 blocks; 512 free (0 chunks); 7680 used
-LOG: level: 1; smgr relation table: 16384 total in 2 blocks; 4544 free (3 chunks); 11840 used
-LOG: level: 1; TransactionAbortContext: 32768 total in 1 blocks; 32504 free (0 chunks); 264 used
+LOG: level: 1; TopMemoryContext: 80800 total in 6 blocks; 14432 free (5 chunks); 66368 used
+LOG: level: 2; pgstat TabStatusArray lookup hash table: 8192 total in 1 blocks; 1408 free (0 chunks); 6784 used
+LOG: level: 2; TopTransactionContext: 8192 total in 1 blocks; 7720 free (1 chunks); 472 used
+LOG: level: 2; RowDescriptionContext: 8192 total in 1 blocks; 6880 free (0 chunks); 1312 used
+LOG: level: 2; MessageContext: 16384 total in 2 blocks; 5152 free (0 chunks); 11232 used
+LOG: level: 2; Operator class cache: 8192 total in 1 blocks; 512 free (0 chunks); 7680 used
+LOG: level: 2; smgr relation table: 16384 total in 2 blocks; 4544 free (3 chunks); 11840 used
+LOG: level: 2; TransactionAbortContext: 32768 total in 1 blocks; 32504 free (0 chunks); 264 used
...
-LOG: level: 1; ErrorContext: 8192 total in 1 blocks; 7928 free (3 chunks); 264 used
+LOG: level: 2; ErrorContext: 8192 total in 1 blocks; 7928 free (3 chunks); 264 used
LOG: Grand total: 1651920 bytes in 201 blocks; 622360 free (88 chunks); 1029560 used
</screen>
If there are more than 100 child contexts under the same parent, the first
--
2.49.0
Attachments:
[text/plain] v1-0001-doc-Fix-memory-context-level-in-pg_log_backend_me.patch (2.9K, ../../[email protected]/2-v1-0001-doc-Fix-memory-context-level-in-pg_log_backend_me.patch)
download | inline diff:
From 7b3aa9de467005e540b2246ed89c9e43fe08f6bd Mon Sep 17 00:00:00 2001
From: Fujii Masao <[email protected]>
Date: Fri, 18 Apr 2025 17:45:29 +0900
Subject: [PATCH v1] doc: Fix memory context level in
pg_log_backend_memory_contexts() example.
Commit d9e03864b6b changed the memory context level numbers shown by
pg_log_backend_memory_contexts() to be 1-based. However, the example in
the documentation was not updated and still used 0-based numbering.
This commit updates the example to match the current 1-based output.
---
doc/src/sgml/func.sgml | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 1c5cfee25d1..574a544d9fa 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -28922,16 +28922,16 @@ One message for each memory context will be logged. For example:
<screen>
LOG: logging memory contexts of PID 10377
STATEMENT: SELECT pg_log_backend_memory_contexts(pg_backend_pid());
-LOG: level: 0; TopMemoryContext: 80800 total in 6 blocks; 14432 free (5 chunks); 66368 used
-LOG: level: 1; pgstat TabStatusArray lookup hash table: 8192 total in 1 blocks; 1408 free (0 chunks); 6784 used
-LOG: level: 1; TopTransactionContext: 8192 total in 1 blocks; 7720 free (1 chunks); 472 used
-LOG: level: 1; RowDescriptionContext: 8192 total in 1 blocks; 6880 free (0 chunks); 1312 used
-LOG: level: 1; MessageContext: 16384 total in 2 blocks; 5152 free (0 chunks); 11232 used
-LOG: level: 1; Operator class cache: 8192 total in 1 blocks; 512 free (0 chunks); 7680 used
-LOG: level: 1; smgr relation table: 16384 total in 2 blocks; 4544 free (3 chunks); 11840 used
-LOG: level: 1; TransactionAbortContext: 32768 total in 1 blocks; 32504 free (0 chunks); 264 used
+LOG: level: 1; TopMemoryContext: 80800 total in 6 blocks; 14432 free (5 chunks); 66368 used
+LOG: level: 2; pgstat TabStatusArray lookup hash table: 8192 total in 1 blocks; 1408 free (0 chunks); 6784 used
+LOG: level: 2; TopTransactionContext: 8192 total in 1 blocks; 7720 free (1 chunks); 472 used
+LOG: level: 2; RowDescriptionContext: 8192 total in 1 blocks; 6880 free (0 chunks); 1312 used
+LOG: level: 2; MessageContext: 16384 total in 2 blocks; 5152 free (0 chunks); 11232 used
+LOG: level: 2; Operator class cache: 8192 total in 1 blocks; 512 free (0 chunks); 7680 used
+LOG: level: 2; smgr relation table: 16384 total in 2 blocks; 4544 free (3 chunks); 11840 used
+LOG: level: 2; TransactionAbortContext: 32768 total in 1 blocks; 32504 free (0 chunks); 264 used
...
-LOG: level: 1; ErrorContext: 8192 total in 1 blocks; 7928 free (3 chunks); 264 used
+LOG: level: 2; ErrorContext: 8192 total in 1 blocks; 7928 free (3 chunks); 264 used
LOG: Grand total: 1651920 bytes in 201 blocks; 622360 free (88 chunks); 1029560 used
</screen>
If there are more than 100 child contexts under the same parent, the first
--
2.49.0
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: Align memory context level numbering in pg_log_backend_memory_contexts()
2025-04-17 12:25 Re: Align memory context level numbering in pg_log_backend_memory_contexts() Rahila Syed <[email protected]>
2025-04-17 21:11 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
2025-04-18 08:54 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() Fujii Masao <[email protected]>
@ 2025-04-18 09:23 ` David Rowley <[email protected]>
2025-04-18 09:45 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() Fujii Masao <[email protected]>
0 siblings, 1 reply; 20+ messages in thread
From: David Rowley @ 2025-04-18 09:23 UTC (permalink / raw)
To: Fujii Masao <[email protected]>; +Cc: Rahila Syed <[email protected]>; pgsql-hackers
On Fri, 18 Apr 2025 at 20:54, Fujii Masao <[email protected]> wrote:
> Shouldn't the example output of pg_log_backend_memory_contexts() in
> the documentation also be updated to use 1-based numbering for consistency?
> Patch attached.
Yeah. I failed to notice we had an example of the output.
Want to take care of it?
David
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: Align memory context level numbering in pg_log_backend_memory_contexts()
2025-04-17 12:25 Re: Align memory context level numbering in pg_log_backend_memory_contexts() Rahila Syed <[email protected]>
2025-04-17 21:11 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
2025-04-18 08:54 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() Fujii Masao <[email protected]>
2025-04-18 09:23 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
@ 2025-04-18 09:45 ` Fujii Masao <[email protected]>
2025-04-21 05:59 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() Fujii Masao <[email protected]>
0 siblings, 1 reply; 20+ messages in thread
From: Fujii Masao @ 2025-04-18 09:45 UTC (permalink / raw)
To: David Rowley <[email protected]>; +Cc: Rahila Syed <[email protected]>; pgsql-hackers
On 2025/04/18 18:23, David Rowley wrote:
> On Fri, 18 Apr 2025 at 20:54, Fujii Masao <[email protected]> wrote:
>> Shouldn't the example output of pg_log_backend_memory_contexts() in
>> the documentation also be updated to use 1-based numbering for consistency?
>> Patch attached.
>
> Yeah. I failed to notice we had an example of the output.
>
> Want to take care of it?
Yeah, I will if you're okay with that!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
^ permalink raw reply [nested|flat] 20+ messages in thread
* Re: Align memory context level numbering in pg_log_backend_memory_contexts()
2025-04-17 12:25 Re: Align memory context level numbering in pg_log_backend_memory_contexts() Rahila Syed <[email protected]>
2025-04-17 21:11 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
2025-04-18 08:54 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() Fujii Masao <[email protected]>
2025-04-18 09:23 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
2025-04-18 09:45 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() Fujii Masao <[email protected]>
@ 2025-04-21 05:59 ` Fujii Masao <[email protected]>
0 siblings, 0 replies; 20+ messages in thread
From: Fujii Masao @ 2025-04-21 05:59 UTC (permalink / raw)
To: David Rowley <[email protected]>; +Cc: Rahila Syed <[email protected]>; pgsql-hackers
On 2025/04/18 18:45, Fujii Masao wrote:
>
>
> On 2025/04/18 18:23, David Rowley wrote:
>> On Fri, 18 Apr 2025 at 20:54, Fujii Masao <[email protected]> wrote:
>>> Shouldn't the example output of pg_log_backend_memory_contexts() in
>>> the documentation also be updated to use 1-based numbering for consistency?
>>> Patch attached.
>>
>> Yeah. I failed to notice we had an example of the output.
>>
>> Want to take care of it?
>
> Yeah, I will if you're okay with that!
Pushed. Thanks!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
^ permalink raw reply [nested|flat] 20+ messages in thread
end of thread, other threads:[~2025-04-21 05:59 UTC | newest]
Thread overview: 20+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-02-15 22:45 [PATCH v19 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v20 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v18 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v13 5/7] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v18 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v19 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v20 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v14 5/7] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v15 5/7] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v12 4/6] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v16 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v19 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2023-02-15 22:45 [PATCH v18 3/5] rename archive-modules.sgml to archive-and-restore-modules.sgml Nathan Bossart <[email protected]>
2025-04-17 12:25 Re: Align memory context level numbering in pg_log_backend_memory_contexts() Rahila Syed <[email protected]>
2025-04-17 14:27 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() torikoshia <[email protected]>
2025-04-17 21:11 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
2025-04-18 08:54 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() Fujii Masao <[email protected]>
2025-04-18 09:23 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() David Rowley <[email protected]>
2025-04-18 09:45 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() Fujii Masao <[email protected]>
2025-04-21 05:59 ` Re: Align memory context level numbering in pg_log_backend_memory_contexts() 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