| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Alexey Kondratov <kondratov(dot)aleksey(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Supply restore_command to pg_rewind via CLI argument |
| Date: | 2021-11-04 12:55:43 |
| Message-ID: | A2118D1E-95C8-4715-93A6-2ADFA9324A38@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 14 Sep 2021, at 16:05, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>> Do we actually need --target-restore-command at all? It seems to me
>> that we have all we need with --restore-target-wal, and that's not
>> really instinctive to pass down a command via another command..
>
> Currently we know that --restore-target-wal is not enough if postgresql.conf does not reside within PGDATA.
That's a useful reason which wasn't brought up in the earlier thread, and may
tip the scales in favor.
The patch no longer applies, can you submit a rebased version please?
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2021-11-04 13:05:30 | Re: Automatic notification of top transaction IDs |
| Previous Message | torikoshia | 2021-11-04 12:49:21 | Re: RFC: Logging plan of the running query |