thales/postgresql_disk_filling_report
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

updates+++++++++++++++

Browse Source
This commit is contained in:
dodger 2023-10-28 09:23:54 +02:00
parent c37591da6c
commit 018b6df18a
Signed by: dodger
GPG Key ID: F5EAC9974313EEC9
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
intervention.md
View File

@ -69,7 +69,7 @@ I had to restart the _primary_ server to apply that config, sorrry for that.
## To be done ## To be done
### Options ### Option #1 for archiving (recommended)
As I say, this is far to be a good solution. As I say, this is far to be a good solution.
In my opinion, the best option will be the one I already mention, map one network drive from one server to the other into `Z:\` and use: In my opinion, the best option will be the one I already mention, map one network drive from one server to the other into `Z:\` and use:
@ -77,6 +77,13 @@ In my opinion, the best option will be the one I already mention, map one networ
archive_command = 'copy "%p" "Z:\\archivelog\\%f"' archive_command = 'copy "%p" "Z:\\archivelog\\%f"'
``` ```
We should investigate permissions for this solution.
### Option #2 for archiving
In the case we can't achieve the #1 solution, I suggest to keep the current configuration and perform the synchronization via _scheduled_ tasks.
So, for example, we will launch `rsync R:\postgresql\local\archivelog 10.6.x.3\R:\postgresql\archivelog` (the syntax will be wrong, I had never used `rsync` on windows...).
To copy archivelogs from one server to the opposite.