Horton

Re: Duplicate history file?

Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>

View thread View on postgr.es
From: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2021-06-08T02:33:16Z
Lists: pgsql-hackers 
On 2021/06/07 17:32, Kyotaro Horiguchi wrote:
>>>> I just noticed that this thread is still tied to another thread
>>>> (it's not an independent thread). To fix that, it may be better to
>>>> create a new thread again.
>>> Mmm. Maybe my mailer automatically inserted In-Reply-To field for the
>>> cited messsage.  Do we (the two of us) bother re-launching a new
>>> thread?
>>
>>
>> The reason I suggested it was because I thought it might be
>> confusing if the threads were not independent when registered in
>> a commitfest. If that is not a problem, then I'm fine with it as
>> is. :-D
> 
> (You can freely do that, too:p)

I should have told you that I would be happy to create a new thread.

Why I didn't create new thread is that because I didn't want people to
think I had hijacked the thread. :)


> Hmm. I found that the pgsql-hackers archive treats the new thread as a
> part of the old thread, so CF-app would do the same.
> 
> Anyway I re-launched a new standalone thread.
> 
> https://www.postgresql.org/message-id/20210607.173108.348241508233844279.horikyota.ntt%40gmail.com

Thank you!


Regards,
Tatsuro Yamada

Commits

  1. Further refinement of stuck_on_old_timeline recovery test

  2. Adjust new test case to set wal_keep_segments.

  3. Adjust new test case to set wal_keep_size.

  4. Fix corner case failure of new standby to follow new primary.

  5. Back-port a few PostgresNode.pm methods.

  6. Allow PostgresNode.pm's backup method to accept backup_options.

  7. Add end-to-end testing of pg_basebackup's tar-format output.

  8. Allow PostgresNode.pm tests to wait for catchup

  9. Delay reading timeline history file until it's fetched from master.