db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-09-16 09:06:18 +02:00
Code Issues Releases Activity

Recommend not placing spool-path within pg_xlog/pg_wal.

Browse Source 
This is generally not a good idea and it can cause problems for PostgreSQL tools such as pg_rewind.
This commit is contained in:
David Steele
2025-04-10 12:08:35 -05:00
committed by GitHub
parent cab4d6fd5c
commit dd3a7d99a7
3 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
doc/xml/release/2025/2.55.0.xml
View File

@@ -334,6 +334,19 @@
<p>Update <setting>unix_socket_directory</setting> to <setting>unix_socket_directories</setting>.</p>
</release-item>
<release-item>
<github-issue id="2600"/>
<release-item-contributor-list>
<release-item-ideator id="martin.marques"/>
<release-item-contributor id="david.steele"/>
<release-item-reviewer id="martin.marques"/>
<release-item-reviewer id="don.seiler"/>
</release-item-contributor-list>
<p>Recommend not placing <br-setting>spool-path</br-setting> within <path>pg_xlog</path>/<path>pg_wal</path>.</p>
</release-item>
</release-improvement-list>
<release-development-list>

5
doc/xml/release/contributor.xml
View File

@@ -760,6 +760,11 @@
<contributor-id type="github">mnullmei</contributor-id>
</contributor>
<contributor id="martin.marques">
<contributor-name-display>Mart&amp;iacute;n Marqu&amp;eacute;s</contributor-name-display>
<contributor-id type="github">martinmarques</contributor-id>
</contributor>
<contributor id="matt.bunter">
<contributor-name-display>Matt Bunter</contributor-name-display>
<contributor-id type="github">mattbunter</contributor-id>

2
src/build/help/help.xml
View File

@@ -342,7 +342,7 @@
<p>The asynchronous <cmd>archive-push</cmd> command writes acknowledgements into the spool path when it has successfully stored WAL in the archive (and errors on failure) so the foreground process can quickly notify <postgres/>. Acknowledgement files are very small (zero on success and a few hundred bytes on error).</p>
<p>The asynchronous <cmd>archive-get</cmd> command queues WAL in the spool path so it can be provided very quickly when <postgres/> requests it. Moving files to <postgres/> is most efficient when the spool path is on the same filesystem as <path>pg_xlog</path>/<path>pg_wal</path>.</p>
<p>The asynchronous <cmd>archive-get</cmd> command queues WAL in the spool path so it can be provided very quickly when <postgres/> requests it. Moving files to <postgres/> is most efficient when the spool path is on the same filesystem as <path>pg_xlog</path>/<path>pg_wal</path>. However, it is not recommended to place the spool path <i>within</i> the <path>pg_xlog</path>/<path>pg_wal</path> directory as this may cause issues for <postgres/> utilities such as <file>pg_rewind</file>.</p>
<p>The data stored in the spool path is not strictly temporary since it can and should survive a reboot. However, loss of the data in the spool path is not a problem. <backrest/> will simply recheck each WAL segment to ensure it is safely archived for <cmd>archive-push</cmd> and rebuild the queue for <cmd>archive-get</cmd>.</p>