Try
Home   >   mailing lists

Re: restore_command return code behaviour - Mailing list pgsql-hackers

From Jean-Christophe Arnu
Subject Re: restore_command return code behaviour
Date
Msg-id CAHZmTm1Bo+ZgP-nP1CxUBTuTbWux_H26P=12Uz1iy6Ey_w8jLQ@mail.gmail.com
Whole thread Raw
In response to Re: restore_command return code behaviour  (Jean-Christophe Arnu <jcarnu@gmail.com>)
Responses Re: restore_command return code behaviour
List pgsql-hackers
Tree view

On friday, 25 jul. 2025 à 09:35, Jean-Christophe Arnu <jcarnu@gmail.com> wrote :
On fri. 25 jul. 2025,  00:01, Jacob Champion <jacob.champion@enterprisedb.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.



Here's a first version of this tiny doc patch.

Hope this is clear enough.
--
Jean-Christophe Arnu
Attachment

pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: Extension security improvement: Add support for extensions with an owned schema
Next
From: Richard Guo
Date:
Subject: A performance regression issue with Memoize