Re: TAP test for recovery_end_command
От | Amul Sul |
---|---|
Тема | Re: TAP test for recovery_end_command |
Дата | |
Msg-id | CAAJ_b97Yc3FXw+f5U+DFpcC10WYwt5Lej4PpPaijQ_UZLVYd0g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: TAP test for recovery_end_command ("Euler Taveira" <euler@eulerto.com>) |
Ответы |
Re: TAP test for recovery_end_command
|
Список | pgsql-hackers |
On Mon, Sep 13, 2021 at 8:39 PM Euler Taveira <euler@eulerto.com> wrote: > > On Mon, Sep 13, 2021, at 10:09 AM, Amul Sul wrote: > > Yeah, added that test too. I triggered the restartpoint via a > CHECKPOINT command in the attached version. > > +# archive_cleanup_command executed with every restart points > +ok( !-f "$archive_cleanup_command_file", > + 'archive_cleanup_command not executed yet'); > > Why are you including a test whose result is known? Fresh cluster does > not contain archive_cleanup_command.done or recovery_end_command.done. > Make sense, removed in the attached version. > +# Checkpoint will trigger restart point on standby. > +$standby3->safe_psql('postgres', q{CHECKPOINT}); > +ok(-f "$archive_cleanup_command_file", > + 'archive_cleanup_command executed on checkpoint'); > > Is this test reliable? > I think yes, it will be the same as you are suggesting a shutdown which eventually performs a checkpoint. That checkpoint on the recovery server performs the restart point instead. Still, there could be a case where archive_cleanup_command execution could be skipped, if there is no record replied after the previous restart point, which could happen in case of shutdown as well. Hope that makes sense. Regards, Amul
Вложения
В списке pgsql-hackers по дате отправления: