From: | Jean-Christophe Arnu <jcarnu(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: restore_command return code behaviour |
Date: | 2025-07-28 08:01:41 |
Message-ID: | CAHZmTm1Bo+ZgP-nP1CxUBTuTbWux_H26P=12Uz1iy6Ey_w8jLQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On friday, 25 jul. 2025 à 09:35, Jean-Christophe Arnu <jcarnu(at)gmail(dot)com>
wrote :
> On fri. 25 jul. 2025, 00:01, Jacob Champion <
> jacob(dot)champion(at)enterprisedb(dot)com> wrote :
>
> Here are the places where I think the details should be added :
> - GUC documentation [1]
> - Backup and Restore [2]
>
> The other mention of restore_command does not involve (or require) return
> code details.
> If there are no objections, I'll start writing a patch proposal on Monday.
>
>
> [1]
> https://www.postgresql.org/docs/18/runtime-config-wal.html#GUC-RESTORE-COMMAND
> : file doc/src/sgml/config.sgml
> [2]
> https://www.postgresql.org/docs/16/continuous-archiving.html#BACKUP-PITR-RECOVERY
> file: doc/src/sgml/backup.sgml
>
Here's a first version of this tiny doc patch.
Hope this is clear enough.
--
Jean-Christophe Arnu
Attachment | Content-Type | Size |
---|---|---|
v1-0001-add-details-on-restore-command-return-code-128.patch | text/x-patch | 1.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Guo | 2025-07-28 08:13:45 | A performance regression issue with Memoize |
Previous Message | Jelte Fennema-Nio | 2025-07-28 08:01:38 | Re: Extension security improvement: Add support for extensions with an owned schema |